G
Guest
I'm running a native Windows Server 2003 network with Windows XP Pro clients.
On occasions, I have the weirdest thing happen where clients won't be able
to access the internet UNLESS they're given an entirely new IP address. I
would find myself always excluding their currently assigned IP address under
the DHCP scope so that when they renew, they're given a new IP address. Once
that's done, they're able to access the internet right away.
I've tried ipconfig /flushdns, removing/reinstalling the NIC, pinging
external websites (i.e. www.yahoo.com and get successfully resolved but get a
request timeout each time), I've tried rebooting the PC.. all to no avail.
The only fix that works is to assign them a new IP altogether. I've grown to
about 30 exclusions under my default scope in DHCP, but I need a reason/fix
for this asap.
I have two DNS servers both running Windows Server 2003. All servers are
running on the latest SP and patches/updates as well as the client PC's.
On occasions, I have the weirdest thing happen where clients won't be able
to access the internet UNLESS they're given an entirely new IP address. I
would find myself always excluding their currently assigned IP address under
the DHCP scope so that when they renew, they're given a new IP address. Once
that's done, they're able to access the internet right away.
I've tried ipconfig /flushdns, removing/reinstalling the NIC, pinging
external websites (i.e. www.yahoo.com and get successfully resolved but get a
request timeout each time), I've tried rebooting the PC.. all to no avail.
The only fix that works is to assign them a new IP altogether. I've grown to
about 30 exclusions under my default scope in DHCP, but I need a reason/fix
for this asap.
I have two DNS servers both running Windows Server 2003. All servers are
running on the latest SP and patches/updates as well as the client PC's.