July 28, 2010 at 5:00 am
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
July 28, 2010 at 5:15 am
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
July 28, 2010 at 5:49 am
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 ??
July 28, 2010 at 6:45 am
The issues is with DNS i think...
Which Edition of SQL Server you using??
July 28, 2010 at 7:04 am
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;-)
July 28, 2010 at 10:44 am
Its a SQL server enterprise edition (64 bit) .
July 29, 2010 at 1:58 pm
It might be using named pipes rather then tcpip.
Try shutting down named pipes
David
July 29, 2010 at 2:52 pm
You can also modify the C:\WINDOWS\system32\drivers\etc\hosts file to add a line like:
127.0.0.1 [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.
July 29, 2010 at 3:19 pm
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.
July 29, 2010 at 8:29 pm
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
July 30, 2010 at 3:11 pm
I had this happen a couple years ago: using the default SQL instance on a server.
Was not a SQL problem, but rather a DNS server issue.
Had to disjoin the domain, wait a couple days (for the DNS server to clear?), then rejoin.
Worked fine after that - of course, I had two days of hell with queries and jobs failing from all over.
Just a couple months ago, we moved the server physically.
It refused to log back in when rebooted - stating the name it has had for 3 years was duplicated on the network.
In 45 mins since I shut it down to move it here, someone store my name?
Hardly likely.
Turns out the DNS server is sure it is there, and unsurprisingly, it has my old IP address. (New location on different router gets different address.)
Ping the name, you get the address, but the pings either fail, or they are returned by the DNS server itself.
While this is a different issue, I think it demonstrates that ping results have to be actually looked carefully at to avoid misunderstandings.
July 31, 2010 at 1:45 pm
Hi
Also check whether the Server got disconnected from the domain. If so add it back to the domain and restart the server.
Thank You,
Best Regards,
SQLBuddy
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply