Network did not assign a network address to the computer 5

[jheiland]

Good evening,

First time poster to this forum. I've been reading through this forum (and others) related to this topic and have tried most of the suggestions I've encountered with no luck. Please allow me to describe my setup:
- Dell 400SC computer running Windows Home Server OS
- Linksys 8-port router/switch
- Netgear RangeMax Wireless G router
- Dell GX-260 computer (Windows XP Pro)
- Dell HP-Pavilion computer (Windows XP Home)
- Dell Dimension 2200 (Windows XP Home)

I'm getting the message (Network did not a assign a network address the the computer) on the Dell GX-260 computer (Service Pack 3, Pentium 4 2.4 GHz, 1 GB RAM, Network adapter: Intel PRO/1000 MT Network Connection).

- I've tried shutting down the entire network, router and cable modem to let every thing reset - no help
- Uninstalled and reinstalled network adapters - no help
- Checked to make sure machine is DHCP enabled - it is
- Checked to make sure router is set to acquire IP addresses dynamically - it is

When I run ipconfig /all, here is the output:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : ALYSSA-GX260
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connect
ion
Physical Address. . . . . . . . . : 00-08-74-F3-D7-4F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.124.200
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IP Address. . . . . . . . . . . . : fe80::208:74ff:fef3:d74f%8
Default Gateway . . . . . . . . . : 169.254.124.200
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : A9-FE-7C-C8
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:169.254.124.200%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Administrator>

C:\Documents and Settings\Administrator>

Note the odd autoconfig IP address of 169.254.124.200. The router acquires addresses in the range of 169.192.1.2 up to 51. Note, when I hook the machine directly up to the Netgear router or try to hook wirelessly to the Netgrear router I still get the same message and no network address is assigned.

Does anyone have any suggestions? Thanks in advance for any help.

Jeff

 

[linney]

Which machine was the ipconfig /all details from?

Are the other machines connecting with each other and do they have this "Node Type . . . . . . . . . . . . : Peer-Peer" or " Subnet Mask . . . . . . . . . . . : 255.255.0.0"

"For all workstations, do an Ipconfig /all at a CMD box. Look at the "Node Type" value. It should say Broadcast, Hybrid or not defined. Anything else is going to be a problem. The best choice for Workgroups is to force a Node Type of Broadcast or Hybrid on all machines:" See the comments about Node Type in this thread.

Home network shares???
thread779-972205

Have a look at this detailed Network Troubleshooter.
Articles & Tutorials / Network Troubleshooting

http://www.windowsnetworking.com/articles_tutorials/trouble/

Have you tried resetting the Winsock back to defaults?

WinXP Connectivity Issues
faq779-4625

Testing in "Safe Mode with Networking" eliminates any third party programs interference.

 

[vacunita]

What happens if you manually set an address in the correct range and subnet? (Obviously one that is not being used)

Does it work then?

Does the router have any kind of limitation as to how many Addresses it can assign?

Or is there MAC address limitation?

Have you tried a different Network card? Maybe the current one is failing?


----------------------------------
Phil AKA Vacunita
----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

 

[BadBigBen]

Run the Network Connection Wizard, that is sometimes needed to get DHCP working on the PC side...

Also, do check out Linney's last link (winsock issue), resetting these does not hurt...

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

How to ask a question, when posting them to a professional forum.

 

[jheiland]

Thanks to everyone for the replies.

linney - the ipconfig info was for the gx-260. The other
workstations have a node type of "hybrid". I forced the
node type on the gx-260 from "peer-peer" to "hybrid",
however, no resolution.

BigBadBen - Reset the Winsock settings - still no luck.
Also reset the IP/TCP settings to no avail. Reran Network
Connection Wizard with no luck.

vacunita - tried to manually set an address in the correct
range but it still didn't work. The ethernet router
appears to be able to assign a large number of addresses
and the user can change that number (currently set to 50).
The wireless router is currently set to assign up to 252
and it appears that the user can change this number also.

I've looked at the ipconfig again on the gx-260 and now the
IP Address and DNS Servers listings both have question
marks (?) next to them. Haven't tried a new network card -
maybe it is failing. I'll look into that.

This is all I can do for tonight. I'll try reading some
more of the info tomorrow from the links linney sent.

Thanks again for all of the help.
Jeff

 

[BadBigBen]

Deinstall (not deactivate, except Windows own) any third party Firewalls, as these block at times DHCP requests, and are still active if deactivated...

about the (?) after the IP addies, hmmm, never seen that one after a reset of the winsocks... just to be safe, rerun the command (CLI / DOS box): netsh winsock reset catalog and see if that corrects the issue...

also we are assuming that the GX260 is in the same WORKGROUP as the rest, if not make sure that it is...

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

How to ask a question, when posting them to a professional forum.

 

[goombawaho]

As mentioned above, but I would elevate it in the troubleshooting steps: It might be quicker/easier to install another network card (either wired or wireless USB) and see if it behaves properly. That would more or less define the problem as being hardware (network card or its software) or a general windows issue.

Try a different cable if you haven't.

 

[linney]

Remember any changes you might make often require a reboot to update the Registry before you continue your testing.

 

[jheiland]

Good evening again all,

Here's the current status based on subsequent suggestions:

BigBadBen - ran netsh winsock reset catalog: no luck
Also rechecked the workgroup name ("THE COLLECTIVE") and it matches all other machines including the server. Could the space in the workgroup name be a problem??

goombawaho - purchased and installed a new network ethernet card today (Netgear GA311): still no luck; same message ("network did not assign a network address to the computer").
Have tried a different network cable: no luck. Have also checked all cables with a network cable checker - all results show paired, synchronous firing on all 8 pins in sequence (straight-through connection type). In addition, the room where the pc resides has 2 data ports, so connected the other data port to the router and then to the pc to no avail. Seems not to be a hardware problem.

linney - thanks for the reminder, have rebooted the machine after every change including registry changes.

Also tried - uninstalling the network usb pci for the wireless connection and reinstalled it: no luck in getting wireless to work.

Haven't yet tried to uninstall the Norton Internet Security which is the 3rd party firewall I'm running). Will do that soon. Side note: all other workstations are using this firewall with no problems. Have checked firewall general rules among various workstations and the the problem pc (GX-260) and they appear to match; in fact, they're probably looser for the problem machine.

Just in case you're interested, below is the latest ipconfig output from the gx-260 machine after doing all of these things (note the new ethernet card connection is named Local Area Connection 6). Question marks still persist for some of the addresses (btw - the subnet mask on the other computers show 255.255.255.0).:

Windows IP Configuration

Host Name . . . . . . . . . . . . : ALYSSA-GX260
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 4:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connect
ion
Physical Address. . . . . . . . . : 00-08-74-F3-D7-4F

Ethernet adapter Local Area Connection 6:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR GA311 Gigabit Adapter
Physical Address. . . . . . . . . : 00-1E-2A-C2-1C-64
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.182.101
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IP Address. . . . . . . . . . . . : ?
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : ?
?
?

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8187 Wireless 802.11g 54M
bps USB 2.0 Network Adapter
Physical Address. . . . . . . . . : 00-14-6C-61-15-F8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.192.248
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IP Address. . . . . . . . . . . . : ?
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : ?
?
?

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : ?
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled


Many thanks again for everyone's help. Will try the uninstall of the Norton firewall later and let you know what happens.

Jeff

 

[vacunita]

The new card practically rules out a hardware problem.

This may be a bit of a reach, but try removing and re-installing the Client for Microsoft Networks from the network connection Properties.

Once I had it get messed up and prevent the correct functioning of networking services.





----------------------------------
Phil AKA Vacunita
----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

 

[BadBigBen]

Something else comes to mind: IPv6 if that is installed, then uninstall it, IPv6 is not needed in a Private Network nor is it widely used on the Internet (may change in the future)...

Q. How do I uninstall the IPv6 protocol for Windows XP with SP1 or later or Windows Server 2003?

A. For the IPv6 protocol for Windows XP with SP1 or later or Windows Server 2003, do the following:

1. Log on to the computer with a user account that has privileges to change network configuration.
2. Click Start, click Control Panel, and then double-click Network Connections.
3. Right-click any local area connection, and then click Properties.
4. Click Microsoft TCP/IP version 6 (for Windows XP with SP2 or later or Windows Server 2003) or Microsoft IPv6 Developer Edition (for Windows XP with SP1), and then click Uninstall.
5. When prompted to confirm the removal of the Microsoft IPv6 Developer Edition or Microsoft TCP/IP version 6 protocol, click OK.

Alternately, from the Windows XP or Windows Server 2003 desktop, click Start, point to Programs, point to Accessories, and then click Command Prompt. At the command prompt, type netsh interface ipv6 uninstall.

To remove the IPv6 protocol for Windows XP with no service packs installed, do the following:

1. Log on to the computer with a user account that has local administrator privileges.
2. From the Windows XP desktop, click Start, point to Programs, point to Accessories, and then click Command Prompt.
3. At the command prompt, type ipv6 uninstall.

Unlike Windows XP and Windows Server 2003, IPv6 in Windows Vista and Windows Server 2008 cannot be uninstalled. However, you can disable IPv6 in Windows Vista and Windows Server 2008 by doing one of the following:
• In the Network Connections folder, obtain properties on all of your connections and adapters and clear the check box next to the Internet Protocol version 6 (TCP/IPv6) component in the list under This connection uses the following items.

This method disables IPv6 on your LAN interfaces and connections, but does not disable IPv6 on tunnel interfaces or the IPv6 loopback interface.
• Add the following registry value (DWORD type) set to 0xFF:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents

This method disables IPv6 on all your LAN interfaces, connections, and tunnel interfaces but does not disable the IPv6 loopback interface. You must restart the computer for this registry value to take effect.[/quote MicroSoft]

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

How to ask a question, when posting them to a professional forum.

 

[goombawaho]

I saw a vista PC once that had the same problem. I put in another network card and still no ip address.

We ended up using the factory restore CD and it worked normally again. Nothing I did would fix it (resetting all the IP stuff, etc).

It might be time for a reload as much as I hate to say that.

 

[linney]

You are not going to get much joy from that machine until you get the IP addressing sorted out. It obviously needs a Subnet of 255.255.255.0 to have any chance of seeing other parts of the Network. A Gateway address to see the Router.

If it fails to allow you to manually set the IP addressing then as the previous poster has stated it may be time to repair the operating system, or backup all your valuable data and do a clean install.

 

[edfair]

After my latest with 98SE I would suggest a reload on the OS per above.

If things that are supposed to fix things don't, then you have a deeper problem.

If you have another drive to experiment with you could use it to at least prove to yourself that it isn't the hardware.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[jheiland]

Hello all, I've got great news - the machine is back in business!

Next thing I tried was uninstalling and re-installing the Client for Microsoft Networks, however, that did not work.

Next, as promised I was going to attempt completely uninstalling my 3rd party firewall (Norton). Had been dreading that because it's a hassle to get back on. So decided to first just try disabling the firewall (hadn't tried that yet) figuring it wouldn't work since it doesn't disable monitoring (which I understand can cause the problem). But that DID work. Once the Norton firewall was disabled, the network connection began working almost immediately.

Frankly, I'm embarrassed that I didn't try that sooner especially since BigBadBen had suggested it in one of the earlier posts. For now, I've re-activated Windows firewall until I can figure out what's up with Norton.

Am sending this post from the (formerly) problem machine and have since gotten it added to my home network and connected to the server.

I want to thank everyone for their patience and bearing with me while working through this problem and also for the most excellent advice given by all. You've provided me with some valuable new tools for future troubleshooting adventures.

And yes, I will be making a contribution to the forum - it was WELL worth it.

Many thanks and best regards,
Jeff

 

[vacunita]

Glad you got it working, and I'm sure Dave will appreciate the donation.


----------------------------------
Phil AKA Vacunita
----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

 

[BadBigBen]

Glad it's up and running and that we where able to assist in both the problem and a bit of education for future troubles, should they arise...



Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

How to ask a question, when posting them to a professional forum.