• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

The "network did not assign a network address" error

danboy

n00b
Joined
May 12, 2007
Messages
15
does some1 no whats wrong:confused: i am using one nvidia nforce networking controller which is connected to a network switch which is connected laptop and i hav a problem with dat and my other network connection is a marvell yukon thingy which is connected to my desktop PC and dat has problems as well. can any1 help? :confused: :confused:
 
Check you router has its DCHP server switched on. If you want you can assign a static IP to your computer.
 
i did build one of da computers myself, but others in the room do the same thing.
1 other thing - dis network does not have a server. and i don't know and/or have the equipment avaliable. thanx for helping though.
 
OK I thought you had a router not a switch. You will need to assign a static IP, to do this go to network connections and double click the network adapter. Click on properties then select "Internet Protocol" then click properties. Click "use the following ip address" and enter 192.168.2.3 for the IP and 255.255.255.0 as the subnet. Click ok and then OK again.

Repeate for the second computer except change the .3 in the ip adress to .4
 
yep, the IP addresses all have to be unique, so the next computer should end with .5, then .6, etc
 
It worked on one computer (mine only) in properties, it changed from packets to bytes, but when I go to view workgroup computers, it only shows mine. also, i ran the network setup on all the computers and named them all MSHOME. if you know anythig, please tell me:confused:
 
the workgroup is all the same on all the computers. on the computer i built, in workgroup computers, i can only see mine, with the laptop, i can see all the computers on the network but can't access them (All firewalls are turned off not internet security) and on the last compaq pc, is says MSHOME is not accessible.
 
Do all of the computer IP adresses start with 192.168.2.xxx?

If they do try pinging them.

Press the Win key + R
Type CMD
Type "ping 192.168.2.xxx"
 
"Pinging with 192.168.2.3 with 32 bits of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
(Something something something)"

It disapprared before I could see what is said at the end, but it did say error or something.
 
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Danny>Ping 192.168.2.3

Reply from 62.25.204.139: Destination net unreachable.
Reply from 62.25.204.139: Destination net unreachable.
Reply from 62.25.204.139: Destination net unreachable.
Reply from 62.25.204.139: Destination net unreachable.

Ping statistics for 192.168.2.3
Packets: Sent = 4, Recieved = 4, Lost = 0 <0% loss>,
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


Where did 62.25.204.139 come from?
When this was tested, all the other computers on the network were switched off.
 
This doesn't make sense: we don't have a DCHP server.
Will NetBUI have any effect once i install it?
 
DOH, for some reason I was look at that as your IP address... I've been working too much.

Anyway, it looks like there might be a problem with your routing / default gateway. Try opening a command prompt (Start -> Run | CMD) and typing: route print

and copy / paste the output. It looks like instead of staying on the 192.168.x.x network, it's trying to go through a the 62.x.x.x address to get to it.
 
Oh man this problem is getting worse !!!!!

That is usually the message you get when you ping through some form of gateway, router or DCHP server.
 
This sucks :(
I'm good at building computers, but is there anyone who knows the solution to this network problem???:confused:
 
So what is your current setup?

Exactly what are you trying to do and what is your current hardware?
 
Back
Top