Link to home
Start Free TrialLog in
Avatar of MonacoAtari
MonacoAtari

asked on

Limited Connectivity after installing new Switch.

I have a network with 11 PCs connected to a Windows 2003 Server. The server is the Primary Domain Controller. They were originally connected though a 10Mb hub. I am currently switching to a new Dell PowerConnect 2324 Switch. Now some of the PCs are saying that the Roaming Profile cannot be found when logging on, and I'm also getting that the computer is connecting with Limited or No Connectivity.

This is only happening on about 3 of the computers, the others logon ok.

Do I need to change something on the server or the PCs?

I have checked the cables and they are ok.

Any ideas?
ASKER CERTIFIED SOLUTION
Avatar of 0xnull
0xnull

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
seems like corrupted winsock try
http://www.snapfiles.com/get/winsockxpfix.html

Also if above doesnt work  then uninstall and reinstall drivers


Ded9
SOLUTION
Avatar of rindi
rindi
Flag of Switzerland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of MonacoAtari
MonacoAtari

ASKER

0xnull - The system is set up so that one of the PCs has a broadband internet connection. I ran ipconfig on the machine that wasn't connecting and I got;

Connection Specific DNS Suffix :
IP Address: 169.254.25.34
Subnet Mask : 255.255.0.0
Default Gateway :

On a machine that is connecting correctly

Connection Specific DNS Suffix : mshome.net [is that right for a machine on a windows domain?]
IP Address: 192.168.0.10
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1

Something is definately screwy with the first one. That machine is set to automatically assign IP address and DNS.

ded9 - Tried that app and it made no difference.

Rindi - It's an Unmanaged Switch, so I don't think there's anything I can change on it.

I'm not sure about the cable. I ran a cable tester and it said it was ok, but I'm not sure if it's CAT5. Will that make a difference?
I've also tried a brand new computer, straight out of the box, first time switch on, on the same port as the faulty one and I'm getting Limited or No Connectivity on that one to, with the following from ipconfig.

Connection Specific DNS Suffix :
IP Address: 169.254.15.151
Subnet Mask : 255.255.0.0
Default Gateway :
Try it on another port, or another cable.
<IP Address: 169.254.25.34
Subnet Mask : 255.255.0.0
Default Gateway :

>



The default gateway is missing in the computer thats not working

Ded9
Actually everything is missing. when the IP address has that type of number the NIC can't find a dhcp server which either means there is no physical connection, the dhcp server isn't configured correctly, the nic is broken etc. etc. etc.
I've since spoken with the Office Manager, who now tells me that one half of the office isn't on CAT5 cable and is using something older. Could this be the problem? I've now connected everything back to the old hub and all is working well. Except now I get Cannot Update Roaming Profile errors when logging off.
For 100bt or above you should allways use at least cat5 cable. The best way to verify is to get some cat5 cable abd connect the not working systems with it.
Thanks guys.

You've all been a great help.

What do I do about closing this and who get's the points?
How to distribute the points is up to you, but it should be based on the answer(s) that helped to answer your Q. You can split the points if you want (there is a "Split Points" button), and then you just click on "Accept" next to those answers that helped (I think it works that way, I haven't yet asked any Q's myself, so I'm not sure what the page looks like to the Askers). There is also a "Grade" you can define. Normally that would be an "A", lower grades are only applicable if you asked for more clarification to a post from an expert because  his post wasn't clear and he didn't answer to your request.
Points are up to you...glad it's fixed, or going to be shortly.

FYI, the 169 address space is automatically assigned by MS Windows when the machine can't get an address automagically.  In order for your machines to all work together in this case, they all need the 192. IP address.  If you get new cables, and it still doesn't work, post back and we'll get you straightend out...