We have a strange network problem with some NT4 servers.

[jheyrman]

We have a strange network problem on our LAN.

At certain times (randomly) our network clients seem to lose their network connection to a server, when this occurs they can't connect to one server but are still able to connect to other servers.
This results in many strange things and errors.

"Disk or network error" (MS-Access)
"Cannot save document you must select another file name" (MS-Word en MS-Excell)
"The file is in use by another user… " (MS-Excell)

As a result of this we started pinging the servers every second from a client PC connected to the same switch as the servers. And we discovered that when this error occurs the server in question gives no replies on the ping command. (Sometimes for more than 15 seconds !)

We discovered now that when we open PcAnywhere sessions to the servers the problem disappears.
When the sessions are open the servers can respond to the ping command at all times and the clients don't lose their network connections to the servers anymore. When we keep the servers very busy (CPU and LAN) then the clients also seem to keep their connections alive.

Here are some specs of the things we have.
Servers:
Poweredge 1300 WinNT 4.0 SP6a (with Intel pro 10/100 LAN card)
Poweredge 4200 WinNT 4.0 SP6a (with 3com 3c980 server LAN card)
Poweredge 2500 WinNT 4.0 SP6a (with Intel 8255xx-based 10/100 LAN card)
Network:
Cisco Ethernet switch model 3524
All servers are connected to this switch and they negotiate 100Mbit Full Duplex.

Things we already tested but didn't help:
We tested with other switches (baystack, 3com) and hubs (Intel)
We changed the cabling.
Forced the auto-negotiation to 100/full 100/half 10/full 10/half
Other network cards (in clients and servers)
Checked out the temp directories on clients (MS KB: Q150943)
We disabled all the power saving on clients (NT4 Server has no power saving)

One strange thing,
We have 1 Compaq sever (Proliant ML370).
This server doesn't seem to have this problem.

Does anyone know of this phenomena or knows a solution?

Best regards
Johan

 

[bigi]

I have seen similar things, though not as extreme as what you are experiencing. Try Microsofts' knowledge base article # Q138365. Using the command: net config server /autodisconnect:-1.

 

[merlinx]

I had simular problems with a NT4.0 do to a Clipper app. The server is used ONLY for this app. Apparently the connections are made, (but not terminated), and re-made over and over again. At a certain point I can no longer ping anything in the entire network...

Then I re-boot the one server and everything works well for about 4 weeks.

If you use your net command in a dos window, you can see if there are simular problems. >If this is the case, you can choose a time period when no one is working and call a net disconnect to set everything to 0.

Hope this helps.