Well that is what I am doing - I am not using anything else. Just it doesn't
want to pick up DHCP anymore from my server. Every other wireless client in
the office has no problem. It appears to only be my WEP enabled network.
The network downstairs that is open and doesn't belong to us works fine and
it allows me to connect to the Internet. It seems that Vista doesn't want to
make more than one hop to get DHCP addresses. I guess this is before it
locates the wireless point and assumes thats the only device it can get to
and therefore it doesn't think "oh hold on perhaps if I cannot get a DHCP
packet from this wireless point should I go off and get one from somewhere
Thats my main problem and its starting to get up in my grill. I know it is
trying to map my network but because my wireless Access Point is plugged into
my switch, which then has a connection from my server which provides DHCP, it
doesn't want to map things any further!!!!!
Help still needed!
> "Rowan Troy" wrote:
> > I managed to get Vista installed on my laptop at work - works fine which is
> > pretty good as I tried to install it at home and it didn't want to know. I
> > was connected to my works wireless network which I set up and it was great.
> > I went home that night connected to my home one - fine no issues. Came to
> > work this morning and it now won't connect to the work one. Says either
> > there is limited or no connectivity or it just allows domain access and won't
> > go out to the Internet.
> > Now I heard somewhere that there is something built into Vista that allows
> > workers who leave their wireless network to connect to other networks but
> > when they return they cannot connect straight away they need to do something.
> > If anyone can tell me what that something is or how to fix this issue please
> > HELP!
> > Its an Intel Pro Wireless 2200BG built in adapter to my Alienware.
> > Thanks
> just used windows vista wireless Configuration from Microsoft