mpdalton
asked on
Cannot register server
I have a client that i connect to thru a VPN.
They have 2 instances of sql server running on the same box. Using remote desktop i can open up enterprise manager on the local machine and connect to both no problem. Also all of the clients in their building can connect to the both no problem.
My problem is, when running enterprise manager on my local machine, i can only connect to the default instance, i cannot connect to the second instance.
The error i get is 'server does not exist or access denied.' i'm definately using the right username and password.
any ideas ?
They have 2 instances of sql server running on the same box. Using remote desktop i can open up enterprise manager on the local machine and connect to both no problem. Also all of the clients in their building can connect to the both no problem.
My problem is, when running enterprise manager on my local machine, i can only connect to the default instance, i cannot connect to the second instance.
The error i get is 'server does not exist or access denied.' i'm definately using the right username and password.
any ideas ?
ASKER
ok, i think it may be the port. can they both run on the same port or do they need to be different ?
Try to run from the command prompt
osql /E /S servername\secondinstancen
If not working have a look at this article of Multiple instances:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag2k/html/MultipleInstances.asp
You'll need the SQL Server 2000 Microsoft Data Access Components (MDAC) stack on the client to get multi-instance connectivity from your client machines
Multiple instances cannot run on the same port. Default instance takes 1433. Run SQL Server Network Utility and select the instance and check the port that it is being assigned to your second instance
osql /E /S servername\secondinstancen
If not working have a look at this article of Multiple instances:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag2k/html/MultipleInstances.asp
You'll need the SQL Server 2000 Microsoft Data Access Components (MDAC) stack on the client to get multi-instance connectivity from your client machines
Multiple instances cannot run on the same port. Default instance takes 1433. Run SQL Server Network Utility and select the instance and check the port that it is being assigned to your second instance
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
brilliant, cheers AustinSeven. Adding the port worked perfectly.
thanks for your response ccsenet, you were a little of track however, i mentioned that all clients were working ok, it was only my machine connecting thru a vpn that was having problems.
thanks for your response ccsenet, you were a little of track however, i mentioned that all clients were working ok, it was only my machine connecting thru a vpn that was having problems.
The second instance does *not* use the same ports as the first instance....