Limited Or No connectivity

Hello Brains,

I have an issue that two fellow Tech's are scratching their head's just like me.

We have just moved office and one PC that is urgently needed has decide that between moving offices it now doesn't want to connect to the network. It comes up with limited or no connectivity.

I've tried a brand new NIC and new drivers to go with it and I'm still getting the problem. I've put the hard drive into an Identical machine and still no joy.

Overall there have been 4 IT staff scratching heads. From outside the box does anyone have any idea what we are missing as this machine is needed on the network before 2pm today?


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dbruntonQuid, Me Anxius Sum?  Illegitimi non carborundum.Commented:
Domain machine?

What does ipconfig show?
Box-ItAuthor Commented:
Hi dbrunton,

It is part of a domain.

The IP config comes back with an autoconfig ip of which is not one of ours.


For network connectivity you will need to follow the OSI model and also take into account other potential issues.
Limited or no connectivity errors may also be related to a fault on the network cable / switch. I would recommend following these steps

1) Try plugging another computer into the same network point and see if it obtains connectivity as expected. If it does not you will probably need to try plugging the cable into a different port on the switch and/or toning and testing the pairs on the cable.
The components that usually play a role here are:
 a) Fly lead to the computer
 b) Wall box / point / jack
 c) Switch Point
 d) Incorrectly crimped cable (Crossover / DIrect) or incorrect protocol (Either A or B)

2) If you are certain that the cable is working then you can try the following:

 a) Limited or no connectivity may be DHCP not being able to allocate an IP. Try and set the IP address manually

 b) Try and boot the computer into safe mode with networking and see if you obtain network connectivity then

 c) Try downloading the Windows XP LSP Fix which is the Winsock 2 fix stack - Google for LSP fix if needed

Summary: if the computer works on a different network point you need to look at the network infrastructure and not at the computer hardware / software
Announcing the Winners!

The results are in for the 15th Annual Expert Awards! Congratulations to the winners, and thank you to everyone who participated in the nominations. We are so grateful for the valuable contributions experts make on a daily basis. Click to read more about this year’s recipients!

The IP address you are picking up is what we call a "Private IP" address - This usually means that the computer is not picking up an IP lease from your DHCP Server.

Try to set a Manual IP address / Static IP Address
Do you need instructions on how to specify an IP address?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dbruntonQuid, Me Anxius Sum?  Illegitimi non carborundum.Commented:
Are the two offices using the same network and the same domain?

If they are not then that is the problem.  The computer can't find the domain it was originally on.
Box-ItAuthor Commented:

Thanks. It is not the cable or socket as other PC's and laptop's work from them.

I know how to set up a static IP so this is no problem. Thanks for all you help above.

I will check any that I have not tried and let you know.

Box-ItAuthor Commented:
Hi guy's,

Seeming as I've been in and out I have just been informed by my Manager that there were not enough IP address to dish out.

This problem is now resolved as my manager has upped the IP range.

To show my appreciation to dbrunton and MultivacX86 I'd like to split the points to both of you.


Errors in the event log, source TCPIP/DNSAPI or the adapter drivername (b57...., e1express?)What I like to do on any network problem....Is to reset it ALL....Open Network Connections in Control Panel>Double click it>Properties, and select the Client for MS networks, and File and Printer Sharing. Select the Uninstall button....Then....Start>run>CMD.exenetsh int ip reset reset.lognetsh firewall resetnetsh winsock resetIn the Device Manager, select View>Show Hidden Devicesstart>run>cmdset devmgr_show_nonpresent_devices=1devmgmt.mscThen remove ALL NIC's from the device manager..More information on that command here....Device Manager does not display devices that are not connected to the Windows XP-based computer back to Network Adapters, and make sure your adapters are all gone, including any older ones. (there will be several ' miniport' devices that are not able to be uninstalled....)Once they are all gone, reboot and let Windows reinstall them...Thats a total rebuild of your network connections, to hopefully correct any problems with Basic connectivity.
Box-ItAuthor Commented:
This turned out to be a lack of IP address available. This has beem resolved.
Thanks, was posting before I saw your last response.....
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.