Win2K looses DCHP ability

[Chip Partaledis]

Greetings,

I have encountered the following problem twice now, and
the only solution the first time appeared to be reloading
the OS on the system. I hope there is a better solution
now.

[Problem] - My network of 4 Win2K systems has a Windows
2000 Pro PC (Soyo Dragon MB, Award Bios, LinkSys Nic,
Win2K SrvPak4) using DHCP that 'lost' it's DHCP config on
a boot. It defaulted to the hard address that APIPA
provides and thus I had no network connection. When I
give my system a manual IP address (it's notmal one) I can
ping out and tracrt, but I get no DNS resolution and
nslookup does not work.

I have disbaled APIPA in the registry and checked the DHCP
server for fault and even replaced the Cat5e cable to no
avail. When the system boots it does no gain a DHCP
address anymore. Status of the LinkSys nic shows packets
Sent but none received, and it HAD been working for some
time.

I do not know how to fix or correct this problem as it
stands other than a reload of the OS (something I'd rather
not do again at this point) nor do I know how to correct
this problem should it happen again.

I have all but exhausted my attempts at removing and
reinstalling NIC(s), drivers, juggling IRQ's and what
not. Any assistance would be greatly appreciated.

Chip

 

[Marina Roos]

Do you have a DHCP-server?
Have you enabled the nics to obtain an IP from this DHCP-server and also
obtain DNS?

Marina

 

[Vladimir Brajovic]

I have encountered the same problem. At times the problem
seem to be intermitent it works for a few minutes and then
stops. From that point on rebooting doesn't help.

I have no idea why this happens. By looking at Services, I
say that the system service "DHCP service" did not start.
I started it manually and regain the network connectivity.
Check if you "DHCP client" service is started, and start
it manually. Let me know what you find out.

I totally simpatize with your frustration. I am two weeks
into this, and this is the first time I am connected again
(sort of).

Vlad

 

[Chip Partaledis]

Greetings,

I have a Netgear FVS318 Router configured to provide DHCP
addressing (works fine and has been) and yes the NICs/PC's
are configured to use DHCP - like I said below, the system
WAS working fine until a reboot and then it lost it.

A possible solution might be to Manually configure the
IRQ's being used to force it but I cannot seem to figure
out how to get Win2K Pro to not use Automatic Settings
under it's configs.

Like I said below as well, this is the second time I have
encountered this problem, the first being most of a year
ago when I simply had to reload the OS and that solved the
problem until it showed up again. I do not know what
causes this to happen nor how to correct it as yet and
it's *really* annoying.

Any help would be appreciated.

Chip Partaledis

-----Original Message-----
Do you have a DHCP-server?
Have you enabled the nics to obtain an IP from this DHCP- server and also
obtain DNS?

Marina

"Chip Partaledis" <[email protected]> schreef in bericht

Greetings,

I have encountered the following problem twice now, and
the only solution the first time appeared to be reloading
the OS on the system. I hope there is a better solution
now.

[Problem] - My network of 4 Win2K systems has a Windows
2000 Pro PC (Soyo Dragon MB, Award Bios, LinkSys Nic,
Win2K SrvPak4) using DHCP that 'lost' it's DHCP config on
a boot. It defaulted to the hard address that APIPA
provides and thus I had no network connection. When I
give my system a manual IP address (it's notmal one) I can
ping out and tracrt, but I get no DNS resolution and
nslookup does not work.

I have disbaled APIPA in the registry and checked the DHCP
server for fault and even replaced the Cat5e cable to no
avail. When the system boots it does no gain a DHCP
address anymore. Status of the LinkSys nic shows packets
Sent but none received, and it HAD been working for some
time.

I do not know how to fix or correct this problem as it
stands other than a reload of the OS (something I'd rather
not do again at this point) nor do I know how to correct
this problem should it happen again.

I have all but exhausted my attempts at removing and
reinstalling NIC(s), drivers, juggling IRQ's and what
not. Any assistance would be greatly appreciated.

Chip

.

 

[Chip Partaledis]

Greetings,

Checking the services was one of the early things I did
when this happened, and the services are all started as
normal. I restarted DHCP Client, DNS Client and even
Workstation Service to no avail, nothing did anything
different. It's acting like it's all working properly,
the system is making it's outbound request for an address,
the Router running DHCP is seeing the MAC address of the
card attached and is replying with it's designated address
but the PC is not accepting the reply from the router
somehow. It's like it's getting lost somewhere, BUT, when
I give it all manual IP configuration, I can ping out and
run TRACERT out to internet machines, like 4.2.2.2 and
other addresses so it is making a 2 way connection.

I'm at wits end on this. very confusing.

Chip Partaledis

-----Original Message-----
I have encountered the same problem. At times the problem
seem to be intermitent it works for a few minutes and then
stops. From that point on rebooting doesn't help.

I have no idea why this happens. By looking at Services, I
say that the system service "DHCP service" did not start.
I started it manually and regain the network connectivity.
Check if you "DHCP client" service is started, and start
it manually. Let me know what you find out.

I totally simpatize with your frustration. I am two weeks
into this, and this is the first time I am connected again
(sort of).

Vlad

-----Original Message-----
Greetings,

I have encountered the following problem twice now, and
the only solution the first time appeared to be reloading
the OS on the system. I hope there is a better solution
now.

[Problem] - My network of 4 Win2K systems has a Windows
2000 Pro PC (Soyo Dragon MB, Award Bios, LinkSys Nic,
Win2K SrvPak4) using DHCP that 'lost' it's DHCP config on
a boot. It defaulted to the hard address that APIPA
provides and thus I had no network connection. When I
give my system a manual IP address (it's notmal one) I can
ping out and tracrt, but I get no DNS resolution and
nslookup does not work.

I have disbaled APIPA in the registry and checked the DHCP
server for fault and even replaced the Cat5e cable to no
avail. When the system boots it does no gain a DHCP
address anymore. Status of the LinkSys nic shows packets
Sent but none received, and it HAD been working for some
time.

I do not know how to fix or correct this problem as it
stands other than a reload of the OS (something I'd rather
not do again at this point) nor do I know how to correct
this problem should it happen again.

I have all but exhausted my attempts at removing and
reinstalling NIC(s), drivers, juggling IRQ's and what
not. Any assistance would be greatly appreciated.

Chip
.

.

 

[Chip Partaledis]

Greetings,

I do not have a Windows 2K Server running DHCP, I am using
the Netgear router described below for that functionality.

Chip

-----Original Message-----
You don't have a server, do you?

Marina

"Chip Partaledis" <[email protected]> schreef in bericht

Greetings,

I have a Netgear FVS318 Router configured to provide DHCP
addressing (works fine and has been) and yes the NICs/PC's
are configured to use DHCP - like I said below, the system
WAS working fine until a reboot and then it lost it.

A possible solution might be to Manually configure the
IRQ's being used to force it but I cannot seem to figure
out how to get Win2K Pro to not use Automatic Settings
under it's configs.

Like I said below as well, this is the second time I have
encountered this problem, the first being most of a year
ago when I simply had to reload the OS and that solved the
problem until it showed up again. I do not know what
causes this to happen nor how to correct it as yet and
it's *really* annoying.

Any help would be appreciated.

Chip Partaledis

-----Original Message-----
Do you have a DHCP-server?
Have you enabled the nics to obtain an IP from this

DHCP-
server and also

obtain DNS?

Marina

"Chip Partaledis" <[email protected]> schreef in bericht
Greetings,

I have encountered the following problem twice now, and
the only solution the first time appeared to be reloading
the OS on the system. I hope there is a better solution
now.

[Problem] - My network of 4 Win2K systems has a Windows
2000 Pro PC (Soyo Dragon MB, Award Bios, LinkSys Nic,
Win2K SrvPak4) using DHCP that 'lost' it's DHCP

config
on

a boot. It defaulted to the hard address that APIPA
provides and thus I had no network connection. When I
give my system a manual IP address (it's notmal one)

I
can

ping out and tracrt, but I get no DNS resolution and
nslookup does not work.

I have disbaled APIPA in the registry and checked the DHCP
server for fault and even replaced the Cat5e cable to no
avail. When the system boots it does no gain a DHCP
address anymore. Status of the LinkSys nic shows packets
Sent but none received, and it HAD been working for some
time.

I do not know how to fix or correct this problem as it
stands other than a reload of the OS (something I'd rather
not do again at this point) nor do I know how to correct
this problem should it happen again.

I have all but exhausted my attempts at removing and
reinstalling NIC(s), drivers, juggling IRQ's and what
not. Any assistance would be greatly appreciated.

Chip


.

.

 

[Marina Roos]

Okay. How does a ipconfig/all look and are they the same on each computer
(apart from the IP it's getting from the router).
Are all these computers directly connected to the router?

Marina

Greetings,

I do not have a Windows 2K Server running DHCP, I am using
the Netgear router described below for that functionality.

Chip

-----Original Message-----
You don't have a server, do you?

Marina

"Chip Partaledis" <[email protected]> schreef in bericht

Greetings,

I have a Netgear FVS318 Router configured to provide DHCP
addressing (works fine and has been) and yes the NICs/PC's
are configured to use DHCP - like I said below, the system
WAS working fine until a reboot and then it lost it.

A possible solution might be to Manually configure the
IRQ's being used to force it but I cannot seem to figure
out how to get Win2K Pro to not use Automatic Settings
under it's configs.

Like I said below as well, this is the second time I have
encountered this problem, the first being most of a year
ago when I simply had to reload the OS and that solved the
problem until it showed up again. I do not know what
causes this to happen nor how to correct it as yet and
it's *really* annoying.

Any help would be appreciated.

Chip Partaledis
-----Original Message-----
Do you have a DHCP-server?
Have you enabled the nics to obtain an IP from this DHCP-
server and also
obtain DNS?

Marina

"Chip Partaledis" <[email protected]> schreef
in bericht
Greetings,

I have encountered the following problem twice now, and
the only solution the first time appeared to be
reloading
the OS on the system. I hope there is a better solution
now.

[Problem] - My network of 4 Win2K systems has a Windows
2000 Pro PC (Soyo Dragon MB, Award Bios, LinkSys Nic,
Win2K SrvPak4) using DHCP that 'lost' it's DHCP config
on
a boot. It defaulted to the hard address that APIPA
provides and thus I had no network connection. When I
give my system a manual IP address (it's notmal one) I
can
ping out and tracrt, but I get no DNS resolution and
nslookup does not work.

I have disbaled APIPA in the registry and checked the
DHCP
server for fault and even replaced the Cat5e cable to no
avail. When the system boots it does no gain a DHCP
address anymore. Status of the LinkSys nic shows
packets
Sent but none received, and it HAD been working for some
time.

I do not know how to fix or correct this problem as it
stands other than a reload of the OS (something I'd
rather
not do again at this point) nor do I know how to correct
this problem should it happen again.

I have all but exhausted my attempts at removing and
reinstalling NIC(s), drivers, juggling IRQ's and what
not. Any assistance would be greatly appreciated.

Chip


.

.

 

[Marina Roos]

Check your DHCP-config in the router. Maybe you need a firmware update or
something? A subnet of 0.0.0.0. sure isn't right.

Marina

 

[M.C. Maguire]

I am seeing the same problem on my MS-W2K Pro laptop.

I was on a road trip and consistently logged in to
Earthlink via dialup for about 10 straight days. Return
to office and laptop was unable to recognize 100baseT LAN.
After awhile the dialup also failed to recognize networks.
Tried hard coding DNS servers in LAN connection. Dialup
was always DHCP with dynamic DNS - can establish
connection and watch packets go across however cannot get
email or other use out of it. Can ping all the DNS
servers in my list by typing IP address but cannot use
domain names.

ipconfig /all

Host name: calvin
Primary Dns Suffix:
Node Type: mixed
IP Routing Enabled: No
WINS Proxy Enabled: No

Ethernet adapter Spaceman_Spiff:

Connection-specific DNS Suffix:
Description: FE574B-3Com 10/100 LAN PCCard-Fast Ethernet
Physical Address: 00-50-DA-D3-D2-01
DHCP Enabled: No
IP Address: 192.168.1.50
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DNS Servers: 192.168.1.50
66.80.130.23
66.80.131.5
64.160.192.170
216.200.176.4
24.221.192.5
24.221.208.5

PPP Adapter Earthlink:

Connection-specific DNS Suffix:
Description: WAN (PPP/SLIP) Interface
Physical Address: 00-53-45-00-00-00
DHCP Enabled: No
IP Address: 209.179.226.139
Subnet Mask: 255.255.255.255
Default Gateway: 209.179.226.139
DNS Servers: 207.217.126.81
207.217.77.82
Netbios over TCPip: Disabled

nslookup

***Can't find server name for address <insert DNS ip
address here for all servers listed above>: No response
from server
***Default servers are not available
Default server: Unknown
Address: 192.168.1.50

-----Original Message-----
Do you have a DHCP-server?
Have you enabled the nics to obtain an IP from this DHCP- server and also
obtain DNS?

Marina

"Chip Partaledis" <[email protected]> schreef in bericht

Greetings,

I have encountered the following problem twice now, and
the only solution the first time appeared to be reloading
the OS on the system. I hope there is a better solution
now.

[Problem] - My network of 4 Win2K systems has a Windows
2000 Pro PC (Soyo Dragon MB, Award Bios, LinkSys Nic,
Win2K SrvPak4) using DHCP that 'lost' it's DHCP config on
a boot. It defaulted to the hard address that APIPA
provides and thus I had no network connection. When I
give my system a manual IP address (it's notmal one) I can
ping out and tracrt, but I get no DNS resolution and
nslookup does not work.

I have disbaled APIPA in the registry and checked the DHCP
server for fault and even replaced the Cat5e cable to no
avail. When the system boots it does no gain a DHCP
address anymore. Status of the LinkSys nic shows packets
Sent but none received, and it HAD been working for some
time.

I do not know how to fix or correct this problem as it
stands other than a reload of the OS (something I'd rather
not do again at this point) nor do I know how to correct
this problem should it happen again.

I have all but exhausted my attempts at removing and
reinstalling NIC(s), drivers, juggling IRQ's and what
not. Any assistance would be greatly appreciated.

Chip

.

 

[M.C. Maguire]

Running netdiag.exe on my machine gives error:

"NETDIAG.EXE - Entry Point not found. The procedure entry
point DnsGetPrimaryDomainName_UTF8 could not be located in
the dynamic link library DNSAPI.dll."

-----Original Message-----
I am seeing the same problem on my MS-W2K Pro laptop.

I was on a road trip and consistently logged in to
Earthlink via dialup for about 10 straight days. Return
to office and laptop was unable to recognize 100baseT LAN.
After awhile the dialup also failed to recognize networks.
Tried hard coding DNS servers in LAN connection. Dialup
was always DHCP with dynamic DNS - can establish
connection and watch packets go across however cannot get
email or other use out of it. Can ping all the DNS
servers in my list by typing IP address but cannot use
domain names.

ipconfig /all

Host name: calvin
Primary Dns Suffix:
Node Type: mixed
IP Routing Enabled: No
WINS Proxy Enabled: No

Ethernet adapter Spaceman_Spiff:

Connection-specific DNS Suffix:
Description: FE574B-3Com 10/100 LAN PCCard-Fast Ethernet
Physical Address: 00-50-DA-D3-D2-01
DHCP Enabled: No
IP Address: 192.168.1.50
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DNS Servers: 192.168.1.50
66.80.130.23
66.80.131.5
64.160.192.170
216.200.176.4
24.221.192.5
24.221.208.5

PPP Adapter Earthlink:

Connection-specific DNS Suffix:
Description: WAN (PPP/SLIP) Interface
Physical Address: 00-53-45-00-00-00
DHCP Enabled: No
IP Address: 209.179.226.139
Subnet Mask: 255.255.255.255
Default Gateway: 209.179.226.139
DNS Servers: 207.217.126.81
207.217.77.82
Netbios over TCPip: Disabled

nslookup

***Can't find server name for address <insert DNS ip
address here for all servers listed above>: No response
from server
***Default servers are not available
Default server: Unknown
Address: 192.168.1.50

-----Original Message-----
Do you have a DHCP-server?
Have you enabled the nics to obtain an IP from this DHCP- server and also
obtain DNS?

Marina

"Chip Partaledis" <[email protected]> schreef in bericht

Greetings,

I have encountered the following problem twice now, and
the only solution the first time appeared to be reloading
the OS on the system. I hope there is a better solution
now.

[Problem] - My network of 4 Win2K systems has a Windows
2000 Pro PC (Soyo Dragon MB, Award Bios, LinkSys Nic,
Win2K SrvPak4) using DHCP that 'lost' it's DHCP config on
a boot. It defaulted to the hard address that APIPA
provides and thus I had no network connection. When I
give my system a manual IP address (it's notmal one) I can
ping out and tracrt, but I get no DNS resolution and
nslookup does not work.

I have disbaled APIPA in the registry and checked the DHCP
server for fault and even replaced the Cat5e cable to no
avail. When the system boots it does no gain a DHCP
address anymore. Status of the LinkSys nic shows packets
Sent but none received, and it HAD been working for some
time.

I do not know how to fix or correct this problem as it
stands other than a reload of the OS (something I'd rather
not do again at this point) nor do I know how to correct
this problem should it happen again.

I have all but exhausted my attempts at removing and
reinstalling NIC(s), drivers, juggling IRQ's and what
not. Any assistance would be greatly appreciated.

Chip

.

.

 

[Larry Brasher]

If local clients are getting IP addresses and remote ones are not, then
most likely its the routing device.
I am not familiar with the switch/router in use but some devices have not
only the ability to perform DHCP relaying but also DHCP capabilities that
can allocate IP addresses for any clients broadcasting for one. I would
first check on this.

I would suggest the following:

1.)Some switches have the ability (spanning tree protocol) to check for
looping conditions that may hamper DHCP requests. Do you have this enabled.
If so, I would check to see if you really need this. It should only be used
for cascading switches.

2.)I would also check each specific router to ensure that ports TCP/UDP 67
and TCP/UDP 68 are not blocked.

3.)I would then setup Netmon on the client to see what it is sending out.

4.) I would then contact Linsys. Maybe they have a firmware upgrade.


Shane Brasher
MCSE (2000,NT),MCSA, A+
Microsoft Platforms Support
Windows NT/2000 Networking