Vista Client unable to obtain DHCP address
i'm not 1 ask questions search , study, pulling hair out!!!!
the issue vista clients renewing dhcp lease, issue being not happening.
enviroment windows 2008 & windows 2003 server. 2003 running dhcp server. workstations mix of xp & vista. issue happening vista machines. ones existing leases connecting leases expire drop out of network 169.254.x.x address. static ip's work fine , current workaround.
after extensive testing can conclude how secuirty \ group policy \ domain related issue. test machine windows 2008 server having same problem, (vista based though). i'm not on site using rdp connection windows 2008. has 2 network cards, 1 fixed ip , other dhcp. connecting static ip connection testing.
my test results far.
if remove machine domain dhcp works, when put domain dhcp stops working.
the problem still exists when firewall removed 3 zones.
the dhcp server issuing addresses client isn't taking them. (if remove least particular machine , ipconfig /renew entry populated on dhcp server, client stays @ 169.254.x.x address).
i have tried windows 2003, windows 2008 , router dhcp server. 3 register address , passes client. client doesn't receive them, or @ least doesn't register them.
a wireshark trace seems indicate working, tcpview, (sysinternals), doesn't show network activity, (but normal think).
i have checked existing global policy's, (which few), nothing in there can cause issue.
i have done various resets of firewall , adapters, uninstalled adapters, disabled ipv6 etc etc.
this don't believe same issue many posts on web vista clients not obtaining ip address. i'm convinced domain \ policy related issue. far i'm aware though nothing has changed, have been making network changes these have been reverted until issue resolved.
two items need highlighting are, ipconfig /renew produces following.
windows ip configuration
an error occurred while renewing interface local area connection : access denied.
also....
the diagnostic policy service produces an access deniedif try , start it.
i think these 2 issues possibly related.
lasty firewall log when switch on produces following, (trucated relevant part).
2010-04-15 12:56:48 allow udp 0.0.0.0 255.255.255.255 68 67 0 - - - - - - - send
2010-04-15 12:56:48 drop udp 0.0.0.0 255.255.255.255 68 67 328 - - - - - - - receive
2010-04-15 12:56:48 drop udp 0.0.0.0 255.255.255.255 68 67 328 - - - - - - - receive
2010-04-15 12:56:48 drop udp 0.0.0.0 255.255.255.255 68 67 328 - - - - - - - receive
2010-04-15 12:56:48 allow udp 192.168.111.251 255.255.255.255 67 68 0 - - - - - - - receive
2010-04-15 12:56:48 drop udp 0.0.0.0 255.255.255.255 68 67 364 - - - - - - - receive
2010-04-15 12:56:48 drop udp 0.0.0.0 255.255.255.255 68 67 364 - - - - - - - receive
2010-04-15 12:56:48 drop udp 0.0.0.0 255.255.255.255 68 67 364 - - - - - - - receive
192.168.111.251 dhcp server.
i haven't included every test i've done included ones think relevant.
so in summary, believe communications dhcp server isn't issue, issue function vista performs change , register dhcp issued address.
any assitance appreicated.
hi,
you can test if issue due gpos using following process:
Windows Server > Group Policy
Comments
Post a Comment