New PC can't get IP address

[GlenMH]

Evening everyone!

Just had a very fun time with a friends new PC - not! Unpacked it, booted up OK, set up user accounts etc. Fun and games started when we tried connecting it to a router to access his broadband internet connection. PC is a new Mesh running XP SP2. Currently no new software has been installed.

I have checked on the router that DHCP is enabled. I get a green light on the relevant port on the router and on the network point on the PC which shows the cable is connected OK. Tried a different cable too, which we proved with another PC.

We checked device manager to see if the network card had any warnings: it didn't.
We checked TCP/IP properties and discovered that it could not get an IP address when set to auto. Manually configured one from the address range from the router. Still no luck.
File sharing and printer sharing is enabled.
Tried with Windows firewall on and off - no joy there either.
When I hover over the connection icon in the system tray, it says "iee 1394, connected, 400mbps". The router only supports 100Mb... Looking at the device manager, the firewire and network adapter are running off the same card. I can't find a setting to limit the speed to 100Mb though.

Anyone got any ideas before I start down the 0870 telephone support line?

Cheers

Glen

[docevi1]

the IEE1394 should be a seperate connector to the network connector and shouldn't be saying connected unless you have something plugged in.

First thing to do is use the Network set up wizard (available in Control Panel) and choose the setup that reflects your router/PC combo (in my case it's page 2, option 1 and it's likely to be the same for you). If that doesn't work (it should) then head into the BIOS to ensure that the NIC is connected and maybe try disabling the IEE1394.

[GlenMH]

docevi1 said:

the IEE1394 should be a seperate connector to the network connector and shouldn't be saying connected unless you have something plugged in.

Yep it is - but fed off the same card. I am getting the right lan icon in the system tray.

docevi1 said:

First thing to do is use the Network set up wizard (available in Control Panel) and choose the setup that reflects your router/PC combo (in my case it's page 2, option 1 and it's likely to be the same for you).

I have tried that one too and I got an hour glass for a very short while and then still no joy, even after a reboot.

docevi1 said:

If that doesn't work (it should) then head into the BIOS to ensure that the NIC is connected and maybe try disabling the IEE1394.

I think we may end up going down this route and see what happens.

Thanks for the prompt response!

Glen

[docevi1]

I've had these problems as well in the past, bloody frustrating aren't they! Random explusion of thoughts that may or maynot be relevant:

Have you tried re-installing the NIC? Disabling IEE1394 in Device Manager? Pinging the router? Are you on the same subnet/network name (i.e. MSHome)? Are you sure the router is working as it should? Is XP set to accept DHCP setups? Have you changed any of the services needed for networking? Is windows firewall still working (SP2 has it switched on in about 3 places from what I've seen)?

[GlenMH]

docevi1 said:

I've had these problems as well in the past, bloody frustrating aren't they!

Oh yes!

docevi1 said:

Random explusion of thoughts that may or maynot be relevant: Have you tried re-installing the NIC? Disabling IEE1394 in Device Manager?

Will try these. The first thing that I will try is opening up the case and making sure the card is seated properly. I know how couriers treat these things....

docevi1 said:

Pinging the router? Are you on the same subnet/network name (i.e. MSHome)?

Can ping the router from another machine. Have tried manually configuring the sub-net mask etc. But I hadn't picked up the need for the same network name.

docevi1 said:

Are you sure the router is working as it should?

Oh yes - proven on all ports and wirelessly using another machine.

docevi1 said:

Is XP set to accept DHCP setups?

Yep. Tried manual config too...

docevi1 said:

Have you changed any of the services needed for networking? Is windows firewall still working (SP2 has it switched on in about 3 places from what I've seen)?

I need to have another play in this area. I haven't found all three places it is switched on. Mind you, looking at the connection properties now don't state "firewalled".

Certainly that gives me some more ideas!

I will let you know later in the week how the fun and games are going!

Glen

[pdV6]

Are you saying that you have a network card that also has a firewire (IEE1394) port on it in addition to the RJ45 connector?

If so, should be a case of telling the NIC to use the RJ45 instead of the IEE1394.

[Plotloss]

if you type ipconfig /all what does it show you?

After that try ipconfig /renew and then ipconfig /all again

Has it changed?

[GlenMH]

pdV6 said:

Are you saying that you have a network card that also has a firewire (IEE1394) port on it in addition to the RJ45 connector? If so, should be a case of telling the NIC to use the RJ45 instead of the IEE1394.

It appears to be one card from the outside of the case. Also, in device manager, the 1394 and network controller have the same make model number which make me think it is a common card. Not sure yet how you tell the NIC which port to use as there was no obvious software with it....

Plotloss said:

if you type ipconfig /all what does it show you? After that try ipconfig /renew and then ipconfig /all again Has it changed?

Tried an ipconfig /release followed by ipconfig /renew and all it said after both was "Windows XP IP Configuration" and no other details...

There are no exclamation marks on either of the devices in device manager either.

Might have to give Mesh a call about this one.

Glen

[pdV6]

What's the make/model of the NIC? Failing that the model number of the Mesh PC?

[guydw]

Plotloss is on the right lines .....

Basically you want IP connectivity - Network names are irrelavant - that is Netbios, and is only for Windows.

So you need to :

First understand that what you are trying to do is correct - so draw your network including which network card you are using..

Then make sure that everything is configured correctly - so ensure physical connectivity is correct, use ipconfig at a command prompt (start/run/cmd) - this will show you what IP address you have, and other details such as DNS and default gateway. What IP address range are you expecting to use ? If you see 169.254.x.x then it is not connected. If you have a DHCP address, ping the gateway - it must work ! No IP address, reboot, still no luck configure an address in the same range (I bet the router is 192.168.0.1 255.255.255.0 - so go for .10) - if still no luck then you have a physical problem, or problem with the router.

Are you going from the PC into the ADSL router ? Are you sure you have the correct cable or are using the right port ? You may need a crossover cable - basically if the pin in the plug at your PC is transmit, the corresponding pin needs to be receive, so if you connect two like ports you need a crossover, or maybe there is another setting that changes the pin setting on the router. Also, check that your network cable work.

Finally, can you get a console connection to the router ? Should connect to the comm port on your pc, use hyperterminal to get a terminal session on the router - are there any othe pc's using the router ?

Obviously if they are then the router's fine.

My money is on a physical issue, or a configuration issue with the network card.

[[k]ar|]

Don't know if this will help, but...

I had an issue with my ThinkPad (XP Pro SP2) where all of a sudden it decided my network had "limited or no connectivity", despite me not having changed anything. Further investigation revealed that it was complaining of being unable to obtain an IP address.

I reset everything and rebooted the router, but no joy. It turned out that there was a problem with the Winsock 2 registry entries, which had to be reset.

I don't know if this will help, but it's worth a try if the other suggestions don't work. Drop to the command line and type this in...

netsh winsock reset

... then reboot.

HTH

[k]

[GlenMH]

All - thanks for all the help - a good refresher for me as it is a long time since I set up my home network!

While I was at work today, he had a chat with Mesh who talked him through the configuration issue - it was a hardware config problem. All sorted, a few gig of music and other files copied over and he is a very happy boy!

A virtual all round!

Glen