LAN connection problem

[Anderson_8]

I have an evo800. After restoring my harddrive with the Compaq Restore CD I have not been able to connect to the school network. It was working fine just before that so I don't think it's a hardware problem. The IP starts with 169. I have checked with the school technicians and they confirmed that it is not a network issue, but were unable to solve the problem. Any suggestions? Thanks

[Ernest Ford]

You're going to have to give us more information. What sort of network are you trying to connect to - 10/100 ethernet or WiFi?

Look in the device manager and see if there are any devices showing as unknown (yellow question marks) or with problems (yellow exclamation marks) - resolve these first.

[Karsten Breivik_1]

Hi. Seems you have a network problem afterall. The IP address starting with 169 indicates windows has used its default "autoconfiguration ip address" which is 169.x.x.x. Verify by doing

Start | Run | cmd | ipconfig

As far as I understand, the whole autoconfiguration IP address can sometimes works as an error code. suggest you google with the whole IP address.

Make sure you have network connection (network lamp blinking, etc).

Then ask the tech guys at school wether they use static (manually configured) IP addresses or if they have a DHCP server (dynamic host configuration protocol) for giving you the IP addresses.

If they use a DHCP server, the 169.x.x.x often means you cannot reach the server for getting an IP address, and so windows just assigned this default address for you. Also it could mean that the address scopen on the DHCP server is full (not very likely, but have seen it). try to do an

ipconfig /release
ipconfig /renew

If however they do not use a DHCP server, you will have to get an address from the sysadmin and configure it manually.

Control Panel | Network ... | Local Area Connection | Properties | Internet Protocol | Properties

[Anderson_8]

thanks for the reply. I am using ethernet connection (have tried several ethernets and outlets but none worked), and the device manager shows no problems.

Our school network uses DHCP server. I've seen the tech guys trying ipconfig /release and ipconfig /renew. Unfortunately these hadn't worked either.

[Ernest Ford]

When you look in the device manager are you seeing an icon for the network adapter?

What version of windows are you running? if it's W2K try removing & reinstalling the network adapter to force the OS to rebuild the ip stack - if it's XP you can't remove the stack (it's part of the OS core) but you can force a rebuild - see this MS Knowledgebase article - http://support.microsoft.com/default.aspx?scid=kb;en-us;299357

[Anderson_8]

There is a device under network adapter and it's working properly (at least that's what it says in Properties). I followed the instructions on the article, did get a reset log file, but still obtained the same IP.

[Jorge Pinto Leite]

Hi

Ask your school technicians how many IP addresses is the DHCP server able to give. Also, check with them if your evo800 must be in same workgroup/domain.

I supposed you've already tried what has been previously posted: uninstall the network card, reboot windows to let him discover it, and so on.

If your OS is WXP or W2K there is an option in TCP/IP settings to show a message if you have limited lan connection: mark it and see if that message shows up.

Keep us updated
Jorge

[Julien Mioni]

Have you tried to reinstall with latest driver ?
Julien

[Anderson_8]

Thanks guys. There is a message of limited/no connection. It has been connected for more than a day, with over 2,000 sent but only about 200 received.

I have tried installing the latest driver, but it does not work.

[Julien Mioni]

Try to ask your school technicians for a fixed IP address. It seems like your DHCP client doesn't works Don't forget to ask for DNS servers to use too.

[John Collier]

Just for grunts and chuckles, try to connect to any other network anywhere else (home, public wireless access point, dial-up internet, etc).

Can you get a connection to and an IP address from any source? If not, then I would think that something has gone terribly wrong with your DHCP client in XP and we need to start looking at it more closely.

By the way, what prompted you to reload the OS in the first place? That is not a normal decision for most people. Perhaps that little bit of info would provide us with a hint to the core of this issue...

[Hrvoje_2]

I was have same proble... then i was find this on some other forum and fix it...

" ive found this killer fix for any winsock/tcpip troubles...works like a charm almost every time...try this link http://news.swzone.it/swznews-9826.php"

[Karsten Breivik_1]

Could be that I am experiencing the same probl now:

The DHCP does not work. I can set the static IP, gw, dns, etc.

I CAN ping a known public server, such as the DNS server at my previous university 129.241.190.190 by IP address only.

I CANNOT ping any host based on a domain name, eg ping vg.no gives me "cannot connect...". This suggests DNS client problems.

However, I cannot telnet/ssh to my other local servers either - even if I use only the IP address.

I'll give it a go with the suggestions mentioned of rebuilding the IP stack.

Spooky...

[Venkatesh_16]

Hi there Anderson,

Try reducing the NIC's speed, follow these steps in case you are using WinXP or 2k in your Notebook:

1. Click Start. Right-click on My Computer and select Properties.
2. Click on Hardware tab.
3. Click on Device Manager button.
4. Click on (+) sign besides Network Adapters.
5. Right-Click on the ethernet device and Select Properties.
6. In the resulting window, click "Advanced" tab, select "Link Speed and Duplex" and from the drop-down menu, select 10Mbps/Full Duplex.
7. Click OK.

After following the steps, configure the TCP/IP to obtain an IP address automatically, restart your PC and see if all is well.

HTH
Venkatesh

[Karsten Breivik_1]

I used the WinsockXPFix.exe program that Hrvoje suggested. And it worked! However, there was an error in the link provieded from Hrvoje. The correct one should be http://news.swzone.it/swznews-9826.php

The WinsockXPFix utility rebuilt the registry settings for the network stack. OK in 10 secs.

Apparantly some other program fiddled with the settings. When the other program was uninstalled, it messed up the registry.

Anderson - I suggest you test this and assign 10 pts to Hrvoje if it works.