| Subject | Re: [firebird-support] Re: FB Connection problems |
|---|---|
| Author | Dan Wilson |
| Post date | 2005-02-16T16:47:45Z |
On 2/16/2005 at 4:02 PM sllimr7139 wrote:
As to ways to determine that the ISP is the problem, have you tried establishing other connections (like SSH or Telnet or whatever) between the client location and the server and seeing whether they stay up? Have you tried running pings between the locations for a while and see how the packet loss looks? Have you had the telco check the line quality (if it's DSL, for example)? Have you checked the network cable that connects the server at the ISP's site? Tried a different port on the Ethernet switch at the server site? I've seen all of these cause errors in the past: sometimes one port on a switch will just go bad, or the cable gets pinched and doesn't work reliably.
I just re-read your post: are you saying that the problem happens to multiple clients at different locations? If so, that would tend to eliminate a single bad DSL or cable link as being the problem and tend to focus attention more on the central site and what might be wrong there. I'd try to see about getting SSH or other connections up and see if they stay up reliably, including from another computer at the ISPs server farm over to the server in question.
HTH,
Dan.
> Hi Dan,I determined that it was an ISP problem because I have a laptop that I connect up to my company's offices when I'm on the road (I set up an SSH tunnel). From one location, I consistently lose connectivity, as I said. When I take the laptop to another location, I stay up all the time. I also see connectivity loss from other computers at that first location as well. That location is served by Starband over a two-way satellite connection, and I am positive that Starband drops packets and does other nasty things quite frequently. I suppose it could be the satellite modem that is dropping the packets and connections, but I am more inclined to think it is just the nature of their service. They claim to have a more reliable (and higher-cost) service available, but I've been unwilling to pay up: I keep hoping terrestrial broadband will become available at that location and I can kiss Starband goodbye. I'm almost at the point of just paying up for a real T-1 and be done with it. In any event, I have not resolved the problem there, I simply live with it.
>
> I'm wondering if there isn't an ISP problem. How were you able to
> determine that the ISP was the problem? What have to done to correct
> that issue?
>
> The server is actually hosted in the ISPs office with their server
> farm. All of the current clients are customers of the ISP, but that
> may change in the future. I need to determine a solution to this
> problem ASAP.
>
As to ways to determine that the ISP is the problem, have you tried establishing other connections (like SSH or Telnet or whatever) between the client location and the server and seeing whether they stay up? Have you tried running pings between the locations for a while and see how the packet loss looks? Have you had the telco check the line quality (if it's DSL, for example)? Have you checked the network cable that connects the server at the ISP's site? Tried a different port on the Ethernet switch at the server site? I've seen all of these cause errors in the past: sometimes one port on a switch will just go bad, or the cable gets pinched and doesn't work reliably.
I just re-read your post: are you saying that the problem happens to multiple clients at different locations? If so, that would tend to eliminate a single bad DSL or cable link as being the problem and tend to focus attention more on the central site and what might be wrong there. I'd try to see about getting SSH or other connections up and see if they stay up reliably, including from another computer at the ISPs server farm over to the server in question.
HTH,
Dan.