Server Duplex Settings (Windows 2000 Server)

G

Guest

We've been advised by Bell that , as a result of output errors and collisions
between our switch and server, that we should change the server setting (NIC)
from our existing standard of Auto Detect to 100 Full Duplex and to hard code
the switch to that setting as well (Auto/Auto). Has anyone ever encountered
this before and did it eliminate any problems with workstation <-> server
communication, or is this even the correct forum for this discussion?
Thanks!!
 
D

David H. Lipman

A networking News Group would be more apropos but.... It is valid advice.

Dave



| We've been advised by Bell that , as a result of output errors and collisions
| between our switch and server, that we should change the server setting (NIC)
| from our existing standard of Auto Detect to 100 Full Duplex and to hard code
| the switch to that setting as well (Auto/Auto). Has anyone ever encountered
| this before and did it eliminate any problems with workstation <-> server
| communication, or is this even the correct forum for this discussion?
| Thanks!!
|
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Slow login after applying Rollup 1 for Windows 2000 SP4 5
Changing NIC Speed/Duplex using GP 1
Server Nic speed 2
Cannot copy files to remote network server 5
NIC Port Settings 2
High Collision Rate 3
Server is unable to allocate memory from the System Paged Pool 2
Broadcom netxtreme gigabit won't connect to gigabit port 0

Top