General discussion

Locked

NT Server Communication

By Harry ·
Small NT Server LAN, have established communication between all Servers but one. This Server can Ping others and be Pinged, by either name or IP. it shows up in the Network Neighborhood and is properly defined in Server anager. Running TCP/IP as a protocol with Static IP addresses. DNS/WINS services are being provided by the PDC. Yet files cannot be accessed on this one Server from any other Server. Attempts to access any folders/files on this Server result in the File Manager locking up. Attempts to copy a file 'from' that Server to another result in the message "Unexpected Network Error". However, a file 'has' been copied from another Server 'to' that Server.

Any ideas?

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

NT Server Communication

by Inspectorclave In reply to NT Server Communication

If you are running NTFS on that server (which I hope you are), then check the NTFS rights for the share. (Right-click on the share, select properties, click on security tab, click the permissions button --- but you already knew that ). By default, the EVERYONE group will have FULL CONTROL access to all files. Some admins remove full control access to the EVERYONE group then assign access to other groups as needed. Check to make sure that the other computers have the appropriate access rights. Also, make sure that the SERVER service is running. Check the event log to see if there is something preventing the server service from running properly. I am guessing that attempting to access the server files from File Manager does not lock the system up completely. It will appear this way, but should timeout after 30-60 seconds and display an error message. That is a symptom of a communication failure between the server and client.

Collapse -

NT Server Communication

by Harry In reply to NT Server Communication

Thanks Inspector, I have checked all of the above already and all are OK. No Event Log Messages except for a timeout. If you look at Task Manager on the Server you are trying to access the trouble Server from, immediately after trying to access any folder it goes into "Not Responding" and won't even allow you to the close Task Manager until the timeout occurs, so virtually it does lock everything up until the timeout.

Collapse -

NT Server Communication

by agibbs In reply to NT Server Communication

I woul double-check your IP configuration; make sure there are no duplicate IP addresses; make sure the netmask is correct, etc. (NT always defaults to a class B netmask of 255.255.0.0 I know I've accidentally left that in there before). But, it sounds like you've probably already done all that. I'd definitely switch out NIC's and see what you get there. Also be sure to check the event log for anything abnormal.

--Aaron

Collapse -

NT Server Communication

by Harry In reply to NT Server Communication

Thanks agibbs, have checked and double-checked...no dup IPs, netmask is OK. The Event Log is only giving me a timeout, not leads on 'why'. Unfortunately this is a converted PC in a lab and the NIC is built into system board...I had been hoping not to have to go that far, but perhaps that's the next step.

Back to Windows Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums