SSMS Server Registration Issue

Question

Post reply

SSMS Server Registration Issue

Vivdix

SSC-Addicted

Points: 457
More actions
March 30, 2010 at 5:04 am

#138038

Hi,
I am able to connect to my remote MSSQL server from another server if I am using server IP address to locate the MSSQL server, but i am unable to connect if I am trying to connect with MSSQL instance name in SSMS.
I am using Windows 2008 data center and firewall is on and I enabled the remote server IP for SQL server port.
Vivek

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Lowell SSC Guru Points: 323518 More actions · Answer 1

sounds like a networking issue;

by remote, you mean over the internet, right? not on the same LAN/network?

if it's over the internet, you'd need to make sure the remote server is exposed and would allow connections from the internet, whether thru NAT or the firewall there using port forwarding.

I'm able to connect to my "home" server that way, but it requires some configuration on the firewall.

see how for each service i want to use, i had to set up a port forwarding in the firewall: i would have to add a port for SQL Server to do the same as some of the other services.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Vivdix SSC-Addicted Points: 457 More actions · Answer 2

Hi,

U r right. It may be firewall issue. But what port I should allow for SSMS? I already allowed sql server port. Both the server on LAN and not exposed to Internet.

Vivek

Lowell SSC Guru Points: 323518 More actions · Answer 3

well the implementation is the same, it's just the specifics; the remote server is on a network that has access to the internet, that's a basic assumption.

that network has a router that handles NAT from the local LAN to the Internet and back, whether it's a cisco router or something home/small office based like netgear/linksys/dlink; they all have the ability to map traffic from the internet on a specific port to be redirected to an internal IP on that port.

the default port for SQL Server is 1433, but you'd need to really get with the remote server's network admin to set up the port forwarding.

==edit==

i would make the sql server listen to more than one port, and use an odd port, like 41433 as well;

then make outside users connect on that odd port;

http://support.microsoft.com/kb/294453

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Vivdix SSC-Addicted Points: 457 More actions · Answer 4

I checked and found that Client Server can't resolve the remote server name when the firewall is on. I think this is the only problem. What should I do to make client server able to resolve remote server name? I am using default firewall of Windows server 2008.

Vivek

Lowell SSC Guru Points: 323518 More actions · Answer 5

the devil is in the details: what does "resolve remote server name" mean;

if it's over the internet, is there a DNS of YourRemoteSQLServer.SomeDomainName.Com, or are you talking about a machine name within a network;

without details, we can't really offer suggestions.

if the firewall is "off", if you ping the remote server, what does the IP start with? 10.?.?.?, 192.168.?.?

those would be LAN ip's and not over the internet....

why do you not connect to the IP instead of the name to avoid the naming issue?

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Vivdix SSC-Addicted Points: 457 More actions · Answer 6

Hi Lowell,

Machines are in local network, They are not over the internet and the reason for not using IP is that I am giving remote machine as the distributor and in replication it only takes SQL server instance name rather than IP.

Vivek

Vivdix SSC-Addicted Points: 457 More actions · Answer 7

Hi Lowell,

Thanks for your efforts. I got it resolved by enabling "Network Discovery (NB-Name-In)" rule ( UDP port 137) in windows 2008 firewall on the remote machine. You can check that target machine NetBIOS name is being resolved or not by issuing the following command on command prompt -

ping -a <target machine IP>

Thanks

Vivek