May 22, 2003 at 2:16 am
It is a long story, and now I have spent too many days trying to debug things, so maybe I can get some help here?
My webhosting company runs an MSSQL, and I have two databases attached to this.
I connect via a LAN to Internet.
Half a year ago there were no problems, I could connect
via ODBC, Microsoft Access, and MSSQL7.0 over Multiprotocol.
Oh yes, I can do this still to our department server running MSSQL7.0
Maybe I shouldn't have updated my client PC running Windows98 with new Microsoft patches. But now my Dell PC running XP is also not connecting
to this server anymore.
I have asked the hosting company several times on several potential issues
that it could be, but their answer is simply that it works for them as they connect their client PC from outside network. They claim they have set up
both Multiprotocol and TCP ports for connections.
I've tried Client Multiprotocol Library and I've tried TCP Library, see
following error messages:
Create a New Data Source to SQL Server
Microsoft SQL Server Login
Connection failed:
SQLState: '01000'
SQL Server Error: 1703
[Microsoft][ODBC SQL Server Driver][Multi-Protocol]ConnectionOpen(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][Multi-Protocol]SQL Server does not exist or access denied.
"Dynamically determine port"
Microsoft SQL Server Login
Connection failed:
SQLState: '01000'
SQL Server Error: 10051
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][Multi-Protocol]SQL Server does not exist or access denied.
Microsoft SQL Server Login
Connection failed:
SQLState: '01000'
SQL Server Error: 10060
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][Multi-Protocol]SQL Server does not exist or access denied.
The server is reachable allright:
C:\DOCUME~1\SFM>ping serve007.hosted.servetheworld.net
Pinging serve007.hosted.servetheworld.net [62.70.14.27] with 32 bytes of data:
Reply from 62.70.14.27: bytes=32 time=47ms TTL=114
Reply from 62.70.14.27: bytes=32 time=43ms TTL=114
Reply from 62.70.14.27: bytes=32 time=45ms TTL=114
Reply from 62.70.14.27: bytes=32 time=42ms TTL=114
Ping statistics for 62.70.14.27:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 47ms, Average = 44ms
C:\DOCUME~1\SFM>ping serve007.hosted.servetheworld.net
C:\DOCUME~1\SFM>telnet serve007.hosted.servetheworld.net 1433
Connecting To serve007.hosted.servetheworld.net...Could not open connection to t
he host, on port 1433.
A socket operation was attempted to an unreachable network.
C:\DOCUME~1\SFM>telnet serve007.hosted.servetheworld.net
Connecting To serve007.hosted.servetheworld.net...Could not open connection to t
he host, on port 23.
No connection could be made because the target machine actively refused it.
C:\DOCUME~1\SFM>telnet serve007.hosted.servetheworld.net 1432
Connecting To serve007.hosted.servetheworld.net...Could not open connection to t
he host, on port 1432.
No connection could be made because the target machine actively refused it.
-------------------
So the question is:
What can this be?
A mismatch of Network Library?
A network filtering problem?
A server setup problem?
Regards, Stig F. Mjølsnes
May 26, 2003 at 12:00 pm
This was removed by the editor as SPAM
May 26, 2003 at 12:15 pm
quote:
Connecting To serve007.hosted.servetheworld.net...Could not open connection to the host, on port 1433.
A socket operation was attempted to an unreachable network.
Check with the hosting company which TCP port numebr they are using for your SQL Server instance? It seems not 1433.
Please also check whether firewall allow traffic from you machine to 1433, and from 1433 to your machine.
Issuing netstat -an from an MS-DOS command window to produces the results showing established connections to SQL Server.
Is your SQL Server instance a named instance?
Edited by - Allen_Cui on 05/26/2003 2:18:50 PM
June 12, 2003 at 1:26 pm
So, the answer to this problem was detected in a quite central filtering router of the campus network. The filter on port 1433 was set up in January responding to the Slammer incident, then later forgotten by the network manager.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply