May 28, 2004 at 4:40 am
I cannot seem to be able to connect to a named instance from one of my dev boxes. I get "does not exsist or denied error" when trying to connect via EM. The password is correct and I have triple checked the name of the server. I cannot even connect to the default server. The two machines are connected to different domains. The server that I wan't to connect from can connect to other servers that the target server is in.
From Server win2k sp4 : SQL2K 32BIT SP3
To Server win2003 datacenter : SQL2K 64 BIT SP3 - Clustered Active - Active
Both servers are using TCP/IP sockets. I can ping the default server and created a Client network alias by supplying the port of the named instance. Still no joy. (If I do not specify the domain name of the default server I cannot get a response when pinging)
Any pointers on this one will help.
Andy.
May 28, 2004 at 4:54 am
did you enter the fully qualified name in EM ?
'MyW2k3SQL2KServer.theotherdomain.theotherdomainsuffix' ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
May 28, 2004 at 5:00 am
Yes
Andy.
May 28, 2004 at 5:15 am
Have you been able to connect to the other DOMAIN any computer??
Sounds like you may be having firewall and/or trust issues between the domains based on what you are showing so far.
Good Hunting!
AJ Ahrens
webmaster@kritter.net
May 28, 2004 at 5:20 am
Yes I can.
I have also connected to the target server (64bit) from another machine on the Client server's same domain.
I am busy doing ipconfig checks on the two....
Andy.
May 28, 2004 at 5:40 am
I think I found the problem. The server that cannot connect has a hot strapped IP with no default "Connection-specific DNS Suffix" therefore you have to fully qualify the servername.
I went to another machine ,on the faulty servers domain , that can connect to the 64bit machine and fully qualified the named instance server. The connection failed. It seems as if you cannot fully qualify a named instance server.
I will have to set the Suffix on the server to the 64bit domain.....Ill try , ill see....
Andy.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy