Page 1 of Network not assigning an IP address, why?

Hey there,

Recently ran a new network cable from my PC in my bedroom to router which is downstairs connected to my main PC. I plugged everything in, came up connected, but then said that the network did not assign an IP address to it. I played about a bit but couldn`t get it to work, so took my PC from my bedroom downstairs connected it to the router with a patch lead and it worked fine and detected the IP address straight away. Back upstairs and again not assigning an IP address. Any idea`s what might be causing the problem? What can I try to get it to work? I`ve tried new patch leads between the PC/router and the wall sockets but that didn`t help.

Thanks

WelshTom

---

"The most overlooked advantage of owning a computer is that if they foul up there`s no law against whacking them around a bit."

My DVD Collection

This item was edited on Sunday, 21st August 2005, 14:57

What network setup do you have? What is serving the IP addresses out? Need more details.

Sorry, got a bit ahead of myself and posted with just a heading! Have updated my original message to include more details now.

Thanks

WelshTom

---

"The most overlooked advantage of owning a computer is that if they foul up there`s no law against whacking them around a bit."

My DVD Collection

Make sure that you have DHCP turned on on the router. That`s the protocol that auto assigns IP addresses so if it`s a posible cause.

Seen a post about this before and it was suggested that the cables in the walls were the wrong type. Something about crossover.

Wall sockets? You have a cat5 network patched into your house? Sounds like a defo cabling problem. The fact that taking the machine to the router and using a patch lead has proved that the DHCP server is running and that the PC is connecting to it. I assume the leads you are using are not crossover cables.


EDIT: Great minds and all ... :-)

This item was edited on Sunday, 21st August 2005, 15:36

I ran the Cat5 cable myself, with a wall socket either end, then used patch cables to connect to the PC/Router. I thought it might be a cabling problem, but I did a test with the 2 wall sockets, 2 patch leads and a small length of the Cat5 cable connecting my main PC to the router and it all worked fine. I`m not using crossover cables, just standard Cat5 cable, Cat5 wall plates and ordinary patch leads. Any other suggestions on what might be causing the problem?

---

"The most overlooked advantage of owning a computer is that if they foul up there`s no law against whacking them around a bit."

My DVD Collection

Hi

is the cabling passing near to any electric equipment e.g. flourescent tubing?

Cat5 UTP is prone to signal degradation when run near electrical sources.

Ste.

........is that gasoline i smell?

hmmm...

What speed is your PC Ethernet card set to? Does it match the router port speed?
Try setting both to 10Mb/Full duplex to test & if it works, bump it up to 100Mb/Full duplex.

Sometimes ports that are not set the same can have problems, especially with Cisco routers (known problem).


SN

`Just Craptacular`

This item was edited on Sunday, 21st August 2005, 22:11

Spiny Norman you are a genius! Set the network card on my PC upstairs from automatic to 10 Mb/Full duplex and it connected no probs! Though when I bumped it up to 100Mb/Full duplex I get the same problem as above, though I have now noticed that the connection is getting assigned an IP address, its not getting assigned a Network Address, not sure if this makes a difference but thought I`d mention it. Any suggestions on how to get it working at 100Mb as I could to with the extra speed?

BTW Thanks to everyone for their suggestions and support, I really appreciate it :D

---

"The most overlooked advantage of owning a computer is that if they foul up there`s no law against whacking them around a bit."

My DVD Collection