Discussion Locked

Unable to Connect to the Server

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Dear Sir/Madam,
I am administering a netwrok that has Win NT4.0 servers and Win95/98 clients. Tha network is a mixure of 10 and 100 mbps connections on UTPs usign Bay Network hubs and switches. The problem is that sometime some of the users cannot connect to the server and they get the message "No domain server was available to validate you password. You may not be able to gain access to some network resources." and when the UTP cable is unpluged from the NIC card and pluged again the user will be able to connect.

What is cuasing this to happen???

Thank you and hope to hear from you soon.

9 replies

by duskos

The problem as you describe it indicates hardware problem. This can be one or more of the following causes:
a) segment length (the total cable in the wall + drop cables should not excede 100 m).
b) bad connections in the wall panel and/or wall boxes (could be caused by worn out punch tool).
c) damaged cable.
d) poor cable quality.
e) interference (if the cable is running parallel with mains power lines).
f) bad or damaged connections (RJ45 plugs) connecting wall boxes with NIC.
g) too much cut insulation and untwisted wires in the distribution panel and/or wall boxes.
h) if your copper cable is connecting two buildings with inappropriate cable (indoor cable instead of outdoor cable). Besides that it is always better idea to connectbuildings with optical cables.

You can ask that your network cabling is tested with professional test equipment which can produce written reports about noise attenuation etc.

by bblunden

I do agree it COULD be a hardware problem. But it sounds more like a networking issue. Are you running DHCP? It sounds like you may be getting IP address conflicts.

To see if this is the issue: go to the server and delete the "lease" for theuser you are having a problem with. Then go to the WIN95 client and go to RUN, WINIPCFG.EXE and then release the IP and reboot. If this works, then it is a DHCP issue.

Good luck.

by netwill

a very popular problem for MS OS!

I know for Cisco switches enabling PortFast fixes this problem.

Might what to check with Bay Network.

by mckaytech

You've received some interesting answers so far, but one additional possibility I thought I would offer is that your NIC cards are failing to autonegotiate properly. If you're using 3Com cards, I would put that at the top of the list.

To test for this, try setting the NIC with explicit settings rather than autonegotiate (for example, on a switch, define 10meg full-duplex). If the problem goes away, you've pretty much confirmed that it's a problem related to autonegotiation failure. In theCisco world, we cure that with modification of the Spanning Tree Protocol on the switch and I would guess there is something similar in the Bay world.

regards!

paul

This discussion is closed to new replies.