Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Database server doesn't connect with the Server Name but connects with the IP address Expand / Collapse
Author
Message
Posted Wednesday, July 28, 2010 5:00 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, May 21, 2014 4:54 AM
Points: 22, Visits: 93
Hi,

We have a SQL 2005 server . When I try to connect the DB server with its name from remote , it doesn't connect. But connects with the IP addres.

same is the case with Remote login from using MSTSC.

Can any one help,, where I should check for the change of the system name or server name

Regards
Kiran
Post #959943
Posted Wednesday, July 28, 2010 5:15 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, November 27, 2013 12:34 AM
Points: 188, Visits: 189
One reason could be that Name reolution is not happening by the DNS server. Check with your Server administrator. Are you able to resolve the IP address to the FQDN.

Check if the following command resolve to your server name: PING -a xxx.xxx.xxx.xxx


Thanks & Regards,
Sudeepta.
http://twitter.com/skganguly
Post #959947
Posted Wednesday, July 28, 2010 5:49 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, May 21, 2014 4:54 AM
Points: 22, Visits: 93



Hi ,
I checked the server name using the PING-axxx.xxx.xxx.xxx . It showed up the FQDN with the correct IP .

So, what else can be checked ??
Post #959957
Posted Wednesday, July 28, 2010 6:45 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, September 15, 2014 5:34 AM
Points: 2,609, Visits: 3,903
The issues is with DNS i think...

Which Edition of SQL Server you using??
Post #959987
Posted Wednesday, July 28, 2010 7:04 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 12:26 AM
Points: 2,840, Visits: 3,963
it should be developers or enterprise edition

-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #960007
Posted Wednesday, July 28, 2010 10:44 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, May 21, 2014 4:54 AM
Points: 22, Visits: 93
Its a SQL server enterprise edition (64 bit) .

Post #960205
Posted Thursday, July 29, 2010 1:58 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 10:04 AM
Points: 129, Visits: 2,419
It might be using named pipes rather then tcpip.
Try shutting down named pipes


David



Post #961000
Posted Thursday, July 29, 2010 2:52 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 12:12 PM
Points: 55, Visits: 279
You can also modify the C:\WINDOWS\system32\drivers\etc\hosts file to add a line like:

[ip address] [database server name]

It'll be specific to only your local computer, but it works and faster than waiting for your SysAdmin to check the DNS entries.

Post #961037
Posted Thursday, July 29, 2010 3:19 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, March 27, 2014 2:54 PM
Points: 212, Visits: 466
From the machine you are connecting from, flush your DNS cache: ipconfig /flushdns

I highly believe its a name resolution issue. In the TCP/IP properties of your NIC, make sure the check box labeled "Register this connection's address in DNS" is checked. It's in the Advanced part then select the tab "DNS". Also make sure the DBS suffix order has your root domains.
Post #961045
Posted Thursday, July 29, 2010 8:29 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, September 11, 2014 2:28 PM
Points: 1,194, Visits: 2,219
Try whether you are able to connect to the Target server from any other server in your network.

Also contact your Windows admin and check whether the Server Name is pointing to the right IP Address in the DNS. If not ask him to update the DNS entry.

Thank You,

Best Regards,
SQLBuddy
Post #961089
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse