LAN connectivity problem with Compaq notebook

Business/IT alignment
Data analysis
Data Management
Data Mining
Data warehousing applications
Desktop management applications
Ecommerce applications
Incident response
Intrusion management
Microsoft Office
Microsoft Windows
Network management software
Network monitoring
Network protocols
Network security
Networking services
Patch management
SQL Server
I have a Compaq EVO n1020v notebook. This works fine in our office LAN and sometimes it does not at all. Office LAN is a workgroup with ICS enabled in win 2K server. If I check the IP of the notebook it shows the IP of the LAN but never connects to the internet, can't access LAN computers/printers/shared folders. If I click the repair option right clicking on the right bottom connectivity icon, it says "can't repair, please contact LAN or ISP administrator". It works fine after plugging in/out the LAN cable once/twice and restarting. I checked each and everything but didn't find anything. Any solution/advise to this would be highly appreciated. Thanks

Answer Wiki

Thanks. We'll let you know when a new response is added.

I would like to add the following to my question:

– The notebook has Win XP Pro(SP 1) installed in it.
– The LAN uses DHCP through Win 2k server.

Discuss This Question: 15  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Nharel
    If internet access is your only problem, it might be a limitation of the firewall. Check to see if you have a limited license for the number of client connections.
    5 pointsBadges:
  • Layer9
    It sounds like the first place I would start is check DNS. If you CAN access hosts on the local subnet, but not on the Internet, then I would assume you are getting a good IP from your DHCP server, but not DNS. I don't like however, the sound of a "repair" (which is just an ipconfig /release - ipconfig /renew) not working unless you unplug the cable. That could be more of a problem, like the NIC is not releasing the address, etc. But for now, I would start by doing an ipconfig /all and confirming you have DNS. Also check to see if you have a Personal Firewall running on the laptop, which can block the DHCP resquestresponse packets. Chris Weber
    0 pointsBadges:
  • Dreamscape
    We happen to use Compaq EVO laptops as well. We have found that these laptops are known for loosing there network connectivity or just plain acting up as far a connections go. The network card drivers just are not stable, no matter the version used. A network card driver reinstall usually works. Sometime we've have to replace the network card. Just another though........ Hope it helps
    0 pointsBadges:
  • Kojones
    I agree with Dreamscape. I have had this same issue with D-Link and other NICs and the solution was to ensure the latest service packs for Windows were installed and the latest drivers for the NIC were installed. I also ran my anti-virus software to ensure I wasn't getting traces of a virus.
    0 pointsBadges:
  • Layer9
    Not that every answer is not a good one, but I really would focus on DNS here. If like you say, you CAN access the LOCAL subnet, but CANNOT access the INTERNET, then it sounds like a DNS issue. Your either resolving local names with a local DNS server that is not forwarding external requests, or you are resolving locally with WINS. Remember, if you can PING local hosts, then I would stop worrying about NIC problems right there. IF you can PING the local hosts, and particularly if you can browse the local subnet, then you can assume either you have a bad Default Gateway, or Bad DNS. Chris Weber P.S I assume you would know if there was some sort of restrictions on your network with regards to outbound access.
    0 pointsBadges:
  • Jcan123
    Another thought on the issue. Check your subnet masks on the Win2k server and on the client and verify that IP address is within subnet range.
    0 pointsBadges:
  • Glenkens
    Can you connect to your computer from any other machine in your workgroup?. If yes, then try immediately after to connect from your machine to any other in the workgroup, this often works. If not, try checking the network cable, this could be bad wiring, especially as you get a connection after unplugging /replugging try using a different cable and or using an ethernet cable tester. (check both ends of the cable). Does the cable fit tightly into the socket? As soon as you have an Internet connection, download (or acquire by other means) SP2 (there will be around 30-35)., then check for hardware updates, this quite often fixes problems of this sort.
    0 pointsBadges:
  • Chippy088
    Guess what. I have just had the same problem and errors on a Private LAN. Errors were indicating connectivity problems, but it was NAT/PAT not configured properly. (Firewalls are a pain sometimes.) Definately check IP addresses and VPN settings, to ensure same subnets etc.
    4,625 pointsBadges:
  • Hedgehog
    Hi BinooDas1234 If it's not a hardware/drivers issue as Dreamscape suggests, I would check if the correct Default Gateway is configured on that machine. Not only DNS can cause problems as Chris indicates, but I have also seen **many** cases where a wrong gateway IP address was configured and prevented proper routing & connectivity. Cheers H
    0 pointsBadges:
  • Layer9
    The reason I did not suggest a NATPAT issue as Chippy suggests, which albeit is a good suggestion, you indicate that all other systems have Internet connectivity, so unless you are using static NAT on the Firewall for individual hosts then that would not be the issue. Also that would qualify as a Internet access restriction, and I assume that would be something you have already looked at. I have seen a bad mask cause issues however. If you have a bad mask, you will normally still be able to access the local subnet, but you won't be able to go beyond your first hop, so that is a good suggestion to check as well not to mention your Gateway settings, however based on your information everyone is using DHCP, so it would be unlikely that you are pulling a different DHCP information than anyone else. Like I said earlier, based upon what information you have provided, I still would look at DNS first, unless of course you have left something out in what your telling us. Chris Weber
    0 pointsBadges:
  • Bigshybear
    I am curious about the "I click the repair option right clicking on the right bottom connectivity icon, it says "can't repair, please contact LAN or ISP administrator". It works fine after plugging in/out the LAN cable once/twice and restarting" That sounds to me like TCP/IP stack issues, specifically DHCP discovery. If you could check the IP address you get the first time you plug the Compaq onto the net. Is it an autodiscovery address? i.e. a 169.x.x.x address?. Then it sounds like after a couple times unplugging the network cable and plugging it back in you finally get a correct address. Is this correct? If so, the problem is most likely the computer, not on the network. The next step I would suggest for you would be running the netsh tcpip stack reset command listed in Microsoft knowledgebase article 299357,;en-us;299357 its non-destructive and can't hurt.
    0 pointsBadges:
  • BinooDas1234
    Thanks to all who have replied. It was a great discussion. But I would like to add something to this. First...I have a very small and simple LAN. No firewall/VPN/NATPAT. Firewall is disabled in the EVO notebook. It gets the IP of the LAN through DHCP. Sometimes it shows me the IP of the LAN but never connects to the LAN. If I try ipconfig release and ipconfig renew it gives me the same IP most of the time. Other Dell notebook works fine...never had this kind of problem. Now I think Dreamscape is right. Now I would reset the tcpip stack as suggested and upgrade to SP2. Thanks again to all who replied.
    10 pointsBadges:
  • Layer9
    If that is the answer, ok, but it makes no sense. Your statements on being able to connect to other systems on the local subnet do not make sense if this is the case. If you can connect with host using NetBIOS on the local subnet, then the idea of reinstalling service packs and TCPIP makes no sense. You already have confirmed TCPIP connectivity well beyond Layer 3 (NetBIOS operates at the Session Layer)IF you can connect locally, so uninstalling and reinstalling would be moot. It certainly doe not apply IF as you say, you have NO problem connecting to local hosts on the local subnet. When examining a problem where local connectivity is operational, but remote connectivity is not, then you want to look at 1.Gateways 2.Subnet Masks 3.Name Resolution When I see our techicians re-installing Operating Systems service packs etc, and I know when they reach that point, it's usually because they have given up troubleshooting the problem. If it works for you, then great, but at that point, it is highly unlikely that you had local connectivity as you suggested. If TCPIP works locally, then it will work remotely, assuming you have a good mask, gateway and DNS. Good Luck Chris Weber
    0 pointsBadges:
  • Stevesz
    You have mentioned running IPCONFIG. Have you runn it as IPCONFIG /ALL? This will give you a lot more information than a straight IPCONFIG. One of the items shown is your lease times, when it was obtained and when it expires. If the lease was not obtained at the time youbooted onto your local network, you are probably using a previously obtained IP address. Should this be the case, run IPCONFIG /RENEW and see if it can obtain a new address. If there is a problem obtaining the new address (as evidenced either by a change in the address and/or the lease times) try using IPCONFIG /RELEASE and reboot. Once you have obtained a valid IP address, check to ensure the gateway is listed properly--it should be, but it doesn't hurt to check. Then check your DNS IP addresses. The DNS should show the address of your internal DNS server or your ISP's servers' IP addresses. If this is good, try to access a site on the Internet. If you can, you have discovered why the problem occurs sometimes, a long living IP address whose lease is not negated by a shutdown or restart. If you cannot access the Internet, time for more trouble shooting. First, ping the machine's IP address. If you cannot get a reply, the problem is communication with your NIC. I don't recall you saying if you had an A/V program, but if you do, and it is Symantec's Norton Internet Security, turn off that firewall. I've seen many cases where this has been a problem. Suddenly it decides that it will not allow any traffic in or out of the machiune and blocks most access to the NIC.(For some strange reason, IPCONFIG usually still works.) Once you have turned off this piece of software, try pinging the network card's IP again. It should work. Once you get replies back from you NIC, the next step it to ping your gateway. Then ping an IP on the Internet which will return a ping (try Google (, or Yahoo ( If successful, try pinging the site by name. It should return an IP address and then the replies from that IP address. If successful, you are all done. If your browser will now not get on the Internet, you have a problem with it. Pinging the NIC checks your connectivity with your network card. Pinging the gateway checks your connection with your network's gateway. A failure here means a problem between the machine and the gateway. It could be a bad cable, or a bad port on your hub or switch. Pinging an outside address ensures you are getting to the outside. Failure means a problem with your router. Reswet the router and check the connections.If still not successful, call your ISP for help. Pinging an outside address checks your DNS. Failure here means a problem with DNS. If you have internal DNS, check that set-up and make sure it is communicating with outside DNS servers sio it can get name resolution for sites it does not already contain within. If you are using external DNS, check with your ISP to enure the correct numbers are being used. If your DHCP is a subset of the range you ahve for internal use, you can always give the laptop a static IP address and try that.This will indicate whether you are having a problem with your DHCP server. I did notice that some have indicated problems with the Compaq drivers. You may wish to get a PC Card NIC, disable the internal NIC and use the PC Card. Steve//
    2,015 pointsBadges:
  • LANAll
    Hi All! Is WinXP reporting that "this connection has limited connectivity" and does the network icon in taskbar come up with the red cross? I've used a few CPQ Evos 1020v and their major problem is with the RJ45 network card socket itself. As reported - LAN connection works sometimes after an unplug/plug cycle. Just give it a try with another PC using the same LAN port/cable and see if these symptomps disappear. Hope this helps
    10 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: