Unsolved
This post is more than 5 years old
6 Posts
0
29318
July 27th, 2005 21:00
Connectivity to 2216
Wanted to be organized with this, so here goes.....
This is Probably something very simple and im just not getting it...
I am having a connectablity issue with a computer on my network.
Here is an illistration of what my office looks like, and how the computers are situated
http://www.clan-boa.com/genesis/office.jpg
My cables are cat-5 and the length is ok.
I have troubleshooted the cables, and they all work.
Ok here is the problem. I am getting "limited or no connectivity" on workstationX
Here is what I have done to solve this problem (remains unsolved)
I Tried putting the cable that runs from the dlink to the powerconnect into workstationX. This solved my connectablity issue, but it does not solve the problem of only having one computer in that room(there needs to be four).
When i have the computer pluged into the switch the light SPD/LINK/ACT is ON and the FDX/HDX is off. after looking through the manual, i have determined that the fdx/hdx light being off means that the cable is running half duplex.
so what i did was went into the computers networking card in windows xp and changed it from auto to 100mbpsfullduplex it still doesnt light up.
Also when i restart the computer, it says its full duplex for a while then that light goes off.
I have tried changing the port that the cable goes into, it still does the same thing.
I also connected mobile workstation/laptop (Y) into the switch and it both of the act///fdx lights are on, but it does not get connectability.
I ran a ping of the server every time i changed something, to no avail.
X is windows xp pro
Y is windows xp pro
server is windows server 2003 for small bussiness
:) 10100111001
This is Probably something very simple and im just not getting it...
I am having a connectablity issue with a computer on my network.
Here is an illistration of what my office looks like, and how the computers are situated
http://www.clan-boa.com/genesis/office.jpg
My cables are cat-5 and the length is ok.
I have troubleshooted the cables, and they all work.
Ok here is the problem. I am getting "limited or no connectivity" on workstationX
Here is what I have done to solve this problem (remains unsolved)
I Tried putting the cable that runs from the dlink to the powerconnect into workstationX. This solved my connectablity issue, but it does not solve the problem of only having one computer in that room(there needs to be four).
When i have the computer pluged into the switch the light SPD/LINK/ACT is ON and the FDX/HDX is off. after looking through the manual, i have determined that the fdx/hdx light being off means that the cable is running half duplex.
so what i did was went into the computers networking card in windows xp and changed it from auto to 100mbpsfullduplex it still doesnt light up.
Also when i restart the computer, it says its full duplex for a while then that light goes off.
I have tried changing the port that the cable goes into, it still does the same thing.
I also connected mobile workstation/laptop (Y) into the switch and it both of the act///fdx lights are on, but it does not get connectability.
I ran a ping of the server every time i changed something, to no avail.
X is windows xp pro
Y is windows xp pro
server is windows server 2003 for small bussiness
:) 10100111001
0 events found
No Events found!
DELL-Cuong N.
1K Posts
0
July 29th, 2005 14:00
Hi, I suspected that this might be an autonegotiation problem between the Dlink or the PC with the PowerConnect switch so I posed the question to a colleague of mine and here is his response:
=======
I looked at the Dlink manual and it runs autonegotiation.
The 2216 ports are in autonegotiate mode. Workstation X (and anything connected to the 2216) must be in autonegotiation mode also. If the Worstation X is forced to 100M full (and therefore no autonegotiation) then it is very likely the switch will not connect or will connect at half duplex and X will stay at full duplex (which is what I believe he is saying he sees when he forces X to 100M).
He should check that all the NICs in his network are set to autonegotiation.
See if he has connectivty from Y to the workstations and server in the other room.
He can also swap the DLINK and the 2216 (but do not change the cables since it sounds like there may be a bad cable from X to the 2216) and see if the problem then occurs on the Dlink to X.
What brand and model NIC is on X? Although we have not heard of any, we can double check if there have been any reported issues with the particular NIC.
======
If you let us know what NIC you are using we will check our test results to see if we have seen any problem with the particular NIC.
Cuong.
Message Edited by DELL-Cuong N. on 08-02-2005 10:00 AM
jeddaka
6 Posts
0
August 1st, 2005 13:00
Machine X is running a boardcom net xtreme 57xx gigabit
Driver Version: 7.73.0.0
Server is running broadcom net xtreme 5751 gigabit
Driver Version: 7.80.0.0
jeddaka
6 Posts
0
August 1st, 2005 15:00
I also updated the drivers on machine X ( Broadcom NetXtreme 57xx Gigabit Controller ) to 7.80.0.0 that didnt help, so I rolled back, and then changed it to 7.86.0.0 drivers that also did not help, so i rolled back again.
also, I the cables are fine, because i can get the computer to connect to the dhcp server if I skip the dlink and run the cord straight into the walljack i putin
and seeing as I changed the switches around... one or the other is not broken
thanks
DELL-Cuong N.
1K Posts
0
August 1st, 2005 20:00
We have not tested with that particular DLINK model but we have tested with other DLINK equipments and do not know of any compatibility issues. Since bypassing either DLINK or PowerConnect seems to work, it seems that perhaps the problem is configuration compatibility between the two. Have you tried making sure that all the devices are configured to do auto-negotiation? Anyway, without more information I'm not able to reproduce your problem, but perhaps tech support will be able to work with you more closely and help you debug the problem.
Cuong.