Unable to access internet after waking Vista

[M. Schneider]

Since installing Vista (Ultimate Edition) when I wake Vista from "sleep"
mode I am no longer able to connect to the internet. I can access my router
and local network but am unable to ping or access anything outside my local
network. The only solution I've found is rebooting the computer at which
point everything will work.

I have a D-Link DGE-530T Gigabit Ethernet Adapter connected by ethernet to a
D-Link DIR-533 router which is connected to my Comcast cable modem. When
Windows XP was installed on this computer I did not have this problem (with
all the same hardware and configuration).

I've tried setting a static IP and even with all Firewalls disabled am
running into this problem. As this issue didn't start happening until
installing Vista it must have something to do with the operating system or
security configurations but I'm at a loss of what to try next.

Does anybody have any suggestions?

Thanks,
Marc

 

[Charles W Davis]

Marc,

Is the D-Link DIR-533 router the correct ID? I can find no reference to it
on the D-Link site.
Second, will it support Windows Vista? Try updating the firmware from
D-Link.

 

[dev]

/M. Schneider/ said:

Since installing Vista (Ultimate Edition) when I wake Vista from "sleep"
mode I am no longer able to connect to the internet. I can access my router
and local network but am unable to ping or access anything outside my local
network. The only solution I've found is rebooting the computer at which
point everything will work.

I have a D-Link DGE-530T Gigabit Ethernet Adapter connected by ethernet to a
D-Link DIR-533 router which is connected to my Comcast cable modem. When
Windows XP was installed on this computer I did not have this problem (with
all the same hardware and configuration).

I've tried setting a static IP and even with all Firewalls disabled am
running into this problem. As this issue didn't start happening until
installing Vista it must have something to do with the operating system or
security configurations but I'm at a loss of what to try next.

Is this by chance a case where the browser is still running when SLEEP
commences?

If so, it happens here on occasion. The fix is to simply close the
browser first (SeaMonkey).