Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Trouble with remote connections EM

Author  Topic 

emisare
Starting Member

2 Posts

Posted - 2004-05-11 : 17:06:14
I've been running SQL2000 & Ent Manager for some time for administration of remote databases for web sites. I am not a DBA by anymeans but have basic knowledge of SQL Server as a developer. I have had no connection problems until recently. All of a sudden I was getting preloginhandshake errors when trying to connect to a remote server. I have installed SP3a and continued to get the error (which I understand gives me the latest MDAC).

I did find a post dealing with set up in the Client Network Utility and so I set up an alias for the server. Before this I just entered the IP address in the Ent Man server registration screen. This did solve the preloginhandshake issue. BTW - only if I specified the port, not using dynamic port detection.

Now that I can connect to the remote server I can't create or alter tables. I can view rows and edit and delete rows but not alter tables in design veiw. I have not tried dropping a table.

Error =
ODBC error: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()).
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation.


This problem only happens from my office, and happens on the two client machines I have with Ent Man installed. At home i have no problem on a fairly similar client set up.

We do have a firewall at the office, but I bypassed it and plugged straight into the router my DSL provider supplied. No change.

Could it be the Time Out related?

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-05-11 : 17:10:12
You've got a network problem. If you can connect to SQL Server, but get disconnected when trying to do certain things, then the problem is outside of SQL Server. It could be the box, but I'm thinking it's a network bottleneck.

Tara
Go to Top of Page

emisare
Starting Member

2 Posts

Posted - 2004-05-11 : 17:17:52
I can perform operations wothout problem on the SQL Server on our local network. Could it be an ISP issue? Maybe I'll take my box home and try it over Road Runner.

Thanks for the response.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2004-05-11 : 17:20:42
It could certainly be at the ISP's end. They should turn a network sniffer on to analyze what is going on. There are some software tools out there than you can use to sniff the network without the actual network sniffer which is expensive hardware.

Tara
Go to Top of Page
   

- Advertisement -