Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

[Microsoft][ODBC SQL Server Driver]Login timeout expired

Status
Not open for further replies.

robatwork

IS-IT--Management
May 15, 2003
107
GB
Hi,

We have SQL server express 2005 on a W2003 server here, and all connect using an access front end, and an ODBC connection. All works fine from here

From a client, using a W7pro laptop, logged in via a VPN, I am getting the following error:
---------------------------
Microsoft SQL Server Login
---------------------------
Connection failed:
SQLState: 'HYT00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Login timeout expired

He is connected via a router-router VPN, and can ping the server.

I telnetted from his PC to the server:1443 and I get a response so the VPN isn't blocking the port. I checked his ODBC and he is using TCP/IP like the rest of us.

I also went into server management studio/analysis and increased ExternalCommandTimeout to 50000 from 3600. It still times out after about 30 seconds

Any ideas on where I can go from here?

thanks
Rob
 
A 30s timeout probably means the TCP connection failed to initiate [the ODBC time out is probably how long the client should wait for a response before assuming the worst].

look in the logs to see what TCP connections are blocked at the same exact time as you try to connect.

 
Thanks - I am an SQL dummy - so can you point me to how I go about analysing the logs ie which log and where?
regards
Rob
 
Oh as a further follow up, I got someone else to connect from their home also via a hardware VPN (on a different subnet of course). They can connect to the SQL database with no problems using the same details I was trying above. The are also on W7 Pro, so I think it's some setting on the PC rather than an SQL problem....any ideas?
 
so I think it's some setting on the PC rather than an SQL problem....any ideas?
firewall

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"

Google Rank Extractor -> Perl beta with FusionCharts
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top