Discussion Locked

WAN/DSL connection problem

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have two clients running W2K server-based WAN over 256K DSL line, bandwidth is adequate, but they still keep getting disconnected from the remote server and, worse, W2K doesn't recognize the disconnect, resulting in multiple sessions per user andauto renaming of terminal-based printers being used by a DOS based app. Any suggestions on either the server side or the DSL provider side?

9 replies

by dmiles

The disconnect problem is pointing towards the printer connections,either a bad cable or the printer driver files have become corrupt and need updating.
Printer servers will somtimes emulate the signal and cause it to disconnect,which in turn will cause a duplication of the ip address.

by ma

We are not using a print server, since only one printer is directly attached to the server. All the remote sites have a printer attached directly to one or more of the terminals, and these are the ones that get renamed with a second user session logging on. If we could eliminate or at least reduce the number of disconnects, the printers would be fine.

by russ werner

If all your programming works on first connection, and problem starts when the connection is disruppted check with your dsl provider. I has simular problems with Verizon's dsl. Verizon was our provider and would stop the communication between us andthem, but would not drop our connection. My NT Server could not recognize this lack of communication since the connection remained intact. The DSL was still connected, the ISP would just stop communications. If I dialed back up all worked fine untilthey did it again. Took us about a month to figure all this out, and we changed ISPs. Seems Verizon took acception to 24/7 operations and would stop our communications. Good Luck...

by Former member

Definately check with your service provider, have them run diags and fix the problem...

by ma

We are trying to help the DSL provider, since they don't know why it's happening either. I need suggestions to help the DSL provider and us find a solution.

by ckilday

MA,
Sounds like there's a "communications breakdown" between the server and W2K, in that the server (or the hosting app) terminates the session, but the news doesn't get back to W2K for a clean break. I recommend getting a sniffer/packet decoder and attach it near the remote server. Look for any exchanges that indicate disconnects. If you have the luxury of owning two devices, put one at each end and check the timestamps to see what's happening when you disconnect at the server. You mayalso be able to install the sniffer at the workstation end, and then monitor the log of the remote server. When you see a disconnect at the server, check the sniffer and see what shows up. If you have intermediate devices, I would move the snifferfrom one to the other to see where your communications breaks down. Best wishes.
- ck

This discussion is closed to new replies.