DHCP eventid: 1003
|
From: Nick on 3 Jun 2010 08:10 We have noticed that one of our XP workstations is logging EventId: 1003 every time it starts: Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 00112F237090. The following error occurred: The operation was canceled by the user. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. This is the same hardware as we have on a number of other workstations which are not seeing this message. I have tried an IPConfig /flushdns & /registerdns but still the same. This does not seem to be causing any problems although the user of this workstation does complain of slow network access at times, not sure if that is just the person complaining or not because network connectivity seems fine to me. Any ideas? Nick
From: Charlie Russel - MVP on 3 Jun 2010 09:11 ipconfig /flushdns isn't going to solve the problem - this isn't a DNS failure. What you could try is ipconfig /release, followed by ipconfig /renew. But I'm more inclined to suspect a network hardware issue. Could be iffy cabling, a failing port on the switch, or a failing NIC on the workstation. Standard troubleshooting here would call for trying the easiest to the hardest fixes until we get a fix. So the ipconfig first, followed by a port change, followed by patch cable, followed by changing out the NIC, including the release/renew pair after each hardware change. If it's in the premisis wiring it's a lot uglier. :-) -- Charlie. http://msmvps.com/blogs/russel "Nick" <NoOne(a)NotHere.com> wrote in message news:%237w0KXxALHA.1892(a)TK2MSFTNGP05.phx.gbl... > We have noticed that one of our XP workstations is logging EventId: 1003 > every time it starts: > > Your computer was not able to renew its address from the network (from the > DHCP Server) for the Network Card with network address 00112F237090. The > following error occurred: The operation was canceled by the user. . Your > computer will continue to try and obtain an address on its own from the > network address (DHCP) server. > > This is the same hardware as we have on a number of other workstations > which are not seeing this message. I have tried an IPConfig /flushdns & > /registerdns but still the same. This does not seem to be causing any > problems although the user of this workstation does complain of slow > network access at times, not sure if that is just the person complaining > or not because network connectivity seems fine to me. > > Any ideas? > > Nick >
From: Nick on 3 Jun 2010 10:55 Thanks Charlie, ipconfig /release and then a reboot solved it. I forgot I would loose remote connection to the workstation after the ipconfig /release, had to get them to reboot it for me. Hence the reason we didn't actuallly do an ipconfig /renew but rebooted instead. Problem now solved, help much appreciated. Nick "Charlie Russel - MVP" <Charlie(a)mvKILLALLSPAMMERSps.org> wrote in message news:910351C9-6B7A-4C41-B8D0-EEEFF70F6A85(a)microsoft.com... > ipconfig /flushdns isn't going to solve the problem - this isn't a DNS > failure. What you could try is ipconfig /release, followed by ipconfig > /renew. But I'm more inclined to suspect a network hardware issue. Could > be iffy cabling, a failing port on the switch, or a failing NIC on the > workstation. > > Standard troubleshooting here would call for trying the easiest to the > hardest fixes until we get a fix. So the ipconfig first, followed by a > port change, followed by patch cable, followed by changing out the NIC, > including the release/renew pair after each hardware change. If it's in > the premisis wiring it's a lot uglier. :-) > > -- > Charlie. > http://msmvps.com/blogs/russel > > > > > "Nick" <NoOne(a)NotHere.com> wrote in message > news:%237w0KXxALHA.1892(a)TK2MSFTNGP05.phx.gbl... >> We have noticed that one of our XP workstations is logging EventId: 1003 >> every time it starts: >> >> Your computer was not able to renew its address from the network (from >> the DHCP Server) for the Network Card with network address 00112F237090. >> The following error occurred: The operation was canceled by the user. . >> Your computer will continue to try and obtain an address on its own from >> the network address (DHCP) server. >> >> This is the same hardware as we have on a number of other workstations >> which are not seeing this message. I have tried an IPConfig /flushdns & >> /registerdns but still the same. This does not seem to be causing any >> problems although the user of this workstation does complain of slow >> network access at times, not sure if that is just the person complaining >> or not because network connectivity seems fine to me. >> >> Any ideas? >> >> Nick >> >
From: Charlie Russel - MVP on 3 Jun 2010 12:51 Uh, yeah, that _will_ kill your remote connectivity! Should have mentioned that, didn't actually think about it and assumed you were local to the workstation. If the problem recurs, I'd start looking at it a bit deeper, see if there's a hardware issue going on here. But otherwise, glad it's back. -- Charlie. http://msmvps.com/blogs/russel "Nick" <NoOne(a)NotHere.com> wrote in message news:%23xZ8czyALHA.348(a)TK2MSFTNGP06.phx.gbl... > Thanks Charlie, ipconfig /release and then a reboot solved it. > > I forgot I would loose remote connection to the workstation after the > ipconfig /release, had to get them to reboot it for me. Hence the reason > we didn't actuallly do an ipconfig /renew but rebooted instead. > > Problem now solved, help much appreciated. > > Nick > > > "Charlie Russel - MVP" <Charlie(a)mvKILLALLSPAMMERSps.org> wrote in message > news:910351C9-6B7A-4C41-B8D0-EEEFF70F6A85(a)microsoft.com... >> ipconfig /flushdns isn't going to solve the problem - this isn't a DNS >> failure. What you could try is ipconfig /release, followed by ipconfig >> /renew. But I'm more inclined to suspect a network hardware issue. Could >> be iffy cabling, a failing port on the switch, or a failing NIC on the >> workstation. >> >> Standard troubleshooting here would call for trying the easiest to the >> hardest fixes until we get a fix. So the ipconfig first, followed by a >> port change, followed by patch cable, followed by changing out the NIC, >> including the release/renew pair after each hardware change. If it's in >> the premisis wiring it's a lot uglier. :-) >> >> -- >> Charlie. >> http://msmvps.com/blogs/russel >> >> >> >> >> "Nick" <NoOne(a)NotHere.com> wrote in message >> news:%237w0KXxALHA.1892(a)TK2MSFTNGP05.phx.gbl... >>> We have noticed that one of our XP workstations is logging EventId: 1003 >>> every time it starts: >>> >>> Your computer was not able to renew its address from the network (from >>> the DHCP Server) for the Network Card with network address 00112F237090. >>> The following error occurred: The operation was canceled by the user. . >>> Your computer will continue to try and obtain an address on its own from >>> the network address (DHCP) server. >>> >>> This is the same hardware as we have on a number of other workstations >>> which are not seeing this message. I have tried an IPConfig /flushdns & >>> /registerdns but still the same. This does not seem to be causing any >>> problems although the user of this workstation does complain of slow >>> network access at times, not sure if that is just the person complaining >>> or not because network connectivity seems fine to me. >>> >>> Any ideas? >>> >>> Nick >>> >> > >
|
Pages: 1 Prev: Lost all permissions under C: drive Next: Migration from Server 2003 Standard to SBS 2008 |