TCP/IP Sockets General Network Error

TCP/IP Sockets General Network Error

Post by SFNQ » Fri, 02 Sep 2005 23:22:02


Getting the TCP/IP Socket General Network Error when trying to connect to an
SQL 2000 database using Access 2002 as a front-end.
Access application hangs and then presents the user with this error.
Verified that ODBC is setup correctly.
Machine can successfully ping SQL Server. by name and IP Address.
Only seems to happen on 1 PC at the moment which is running Windows 2000 SP4
 
 
 

TCP/IP Sockets General Network Error

Post by Dennis Bla » Fri, 02 Sep 2005 23:35:49

Is SQL server listening on default port 1433? If yes try running the
following command from a console window

PROMPT> telnet sqlserverHostIP 1433

If you see a blank screen that means that your machine and connect to
SQL server on the required port. If you get an error, make sure there
are no firewalls on that machine.


If you see a blank screen, that means something is wrong in your ODBC
configuration. Try connecting from a third party tool such as WinSQL
( http://www.yqcomputer.com/ ) and see if you see similar behaviour

 
 
 

TCP/IP Sockets General Network Error

Post by SFNQ » Sat, 03 Sep 2005 02:58:08

Yes, SQL Server is listening on port 1433. There are no firewalls on the
machine.
The strange thing is the user was able to use the application until a few
days ago.
Nothing has changed on the client PC or the SQL Server.
 
 
 

TCP/IP Sockets General Network Error

Post by Dennis Bla » Sat, 03 Sep 2005 22:21:03

Did you try using WinSQL and see if that connect? This would give you an
idea if this is a network issue or your application issue