> ATM when I type in
http://192.168.1.2 (the address of the access
point)
> or try to ping it I am unable to connect in browser or ping it. Yet
> the PC that is hard wired from that access point is still connected to
> the network and I can surf the net with it?
>
> Well i appreciate any comments or suggestions!
Hi Chaser. I had an almost identical problem this past weekend (I like
to call it my Christmas "surprise"). It would work, then not, then
work. I'd set everything and boom on the next reset even the SSID was
gone.
What I did wound up being pretty involved but I have two thoughts:
It could be your access point (since you can't ping it) has DHCP set up
and your laptop has a static ip set out of it's range. I thought I had
that problem because of a constant "acquiring address" state even
though I knew damn well the access point expected a static IP which the
laptop had.
But....
It turned out to be XP SP2 and it's stupid, stupid Pavlov like
insistence on the built in firewall. For some reason it hates the
MICROSOFT wireless card in the laptop. Even tho the firewall was off, I
had to go into the advanced settings and turn everything on manually to
get it to work correctly. Status > Properties > Advanced > Settings and
ticked everything but for remote assistance. It may be a laptop kind of
thing because I didn't have to do that at all when I installed SP2 on
the XP box I use as a server. Now I'm all fat and happy - I'm posting
this via the laptop in question even numerous restart cycles and a trip
to my mother-in-laws house to fix her network.
So I'd try something like that - couldn't find anything about it in the
knowledge base at MS, btw.
Max