November 20, 2007 at 3:20 pm
Surface area Configuration - remote connections enabled on both
My developer edition can connect to two other SQL Servers on the network just fine. The other SQL Server box can also connect to these two servers.
SQL Server trial edition sees the other server (dev edition) just fine when I go through the connect to a DB engine dialog. (The opposite is not true.)
Yet I'm still getting error 40 / error 53.
There's gotta be something simple I'm missing. My guess is something on the Windows level. Any ideas?
If it makes any difference, I'm running Vista Home premium on the Dev edition machine and XP Pro on the box with trial edition. Also, I'm using SQL Server authentication.
November 20, 2007 at 4:15 pm
I'm assuming that's XP Pro 64, since that's the only one that technically can run the trial edition (according to system requirements).
error 40 / error 53 usually means "no one there when I call", i.e. path not found, i.e. I can't find the machine.
A few things (probably basic, but let's put them out there anyway):
- which protocol did you enable through "allow remote connections"? in what order?
- did you use just the IP address and instance name?
- the personal firewalls (XP/Vista) both consider named pipes part of "file and print sharing". if you don't have those enabled AND allowed through the firewalls, you might have trouble.
- turn on and if need be allow through FW's the SQL Browser service
- take a look in the SQL Server config manager, at the "Network config"/Protocols. use the IP address and port on the machine that cannot be connected to, and create a client alias to that on the remote machine.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply