Limited Connectivity in a Network Enviorment
Home > IT Answers > Networking > Limited Connectivity in a Network Enviorment
Sterling01
10 pts.
0
Q:
Limited Connectivity in a Network Enviorment
Network connectivity, Windows Server 2003, DHCP, NIC, Network Interface Cards
I have been having this problem on serveral PC's. I have to setup up a new PC on our network and i am getting a limited connectivity error on the NIC card. I have checked all the setting on the PC. I tride to use another PC and i got the same error. I looked into the SP2 error and the recommended fixes are not helping. We are using DHCP on server 2003. Everytime i plug a new PC into the network i get limited connectivity on the card. I have not even add the PC into the domain. (because I cannot) I gave a static IP and the error went away but i cannot even get out to the internet.
I dont know what else to checkk.

thanx
ASKED: Aug 10 2009  2:11 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
BladeStorm
15 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
Winsock Corruption

You may want to check to see if Winsock has become corrupted. Open a command prompt (Start menu -> Run -> cmd -> OK) and attempt to renew your IP address manually.

ipconfig /renew


If you get an error specifying the DHCP server is unavailable/unreachable, then the information below may be relevant (although your attempt to set up a static IP on the network card indicates this may not be the case. You may also get:

"An error occurred while renewing interface ‘Local Area Connection’: An operation was attempted on something that is not a socket."

If this occurs it means Windows Sockets (winsock) may be corrupt. The next step would be to confirm this using "netdiag /test:winsock" in the same command prompt. If the test does not pass, you will probably want to run the fix provided by Microsoft (or the manual steps in the same article) here:

http://support.microsoft.com/kb/811259

DHCP or IP Issues

It sounds like the address pool may be completely used on your DHCP server. Check the address pool to ensure that you have enough addresses to lease out to your current computer population. If you cannot get out to the internet when assigning a static IP address it could be that either your subnet mask is incorrect or the default gateway is missing. Another thing to check when assigning a static address is DNS. You need to have DNS specified when a static address is assigned. Please also provide your operating system information if these issues still continue.
Last Answered: Aug 10 2009  2:57 PM GMT by BladeStorm   15 pts.
Latest Contributors: Labnuke99   26290 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

BlankReg   11280 pts.  |   Aug 10 2009  5:41PM GMT

I would go with Labnuke99’s answer, this has all the signs that it is a DHCP issue, and there are not enough addresses in the pool for the number of PCs you have. Increase the size of the pool, making sure you exclude any fixed addresses you are using, and see if the problems go away.

 
0