I have a bunch of servers on a different subnet.
All of them connect within a second or so except one.
A 64 bit 2008 enterprise version.
Takes about 20 seconds to connect to it through SSMS from my desktop.
Clicking on the server properties gives the same 20 second delay.
Sometimes I get a popup from taskbar area thats says something like "sql
server is waiting for an internal response if this continues to happen tell
Microsoft".

All the protocols are open.
This server in dns is registered as sver.win.xxx.com
The others are registered as sver.xxx.com

Other servers are also 08 64bit. This is the only enterprise 64bit 08 box.
I disabled the servers windows firewall, no change.

Any guesses to the problem or ways to diagnose would be appreciated.

Chuck (nospam34 (AT) nospam (DOT) nospam) writes:
What ping times do you have this server? How well does it browse shares
on this server? What happens if you run SQLCMD? Is this equally slow?
Any difference if you connect with Windows authentication or SQL
authentication? Any encryption in the mix?



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Were you able to resolve this issue? I have the same configuration as you
and the same problem. Thanks!


"Chuck" wrote:

Jim (Jim (AT) discussions (DOT) microsoft.com) writes:
It probably helps if you post the details about your problem.

Does it happen if you connect both with SQL authentication and Windows
authentication?


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

A random guess -- The client has both IPv4 and IPv6 protocols. The version
it tries first is timing out. The version it tries second is succeeding.
--
Rick Byham, MSFT
(Implies no warranty or rights)


"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote

I've expected same problem and found that it is related to Windows Firewall. Try stop it on both side (net stop bfe) and check if the problem has gone. If yes - than configure windows firewall to allow server's communication.