April 2, 2009 at 2:36 am
I Replaced computer of secondary domain, which is also a sql server.
Name of the pc is same as erlier name.
SQL installation did not give problem or error.
but i cannot connect to sql server in enterprize as well query analyzer through its name. error registration failed... and SQL server does not exist or access denied [TCP/IP socket error]...
I can connect thru IP address but not through name.... server name is A002... i cannot connect thru A002... it is secondary domain.. the old pC was also secondary domain with same name.. old PC is not in the network currently
application that uses the database created on this server also behaves in same fations... in a path file if i put name it says server does not exist but if i put ip address it connects.
please opine.
April 2, 2009 at 6:44 am
Sounds like a DNS name resolution error to me. The DNS record for A0002 still probably resolves to the old IP address. What ip address does A0002 resolve to if you go to the command prompt and ping A0002?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
April 2, 2009 at 10:40 am
Sounds like DNS issues as well
Try a nslookup IP_ADDRESS in command prompt to see if it resolves to a name?
April 3, 2009 at 1:51 am
i can ping to A0002 by name as well by ip address.
New PC is having the same ip.
Old PC has been given diff ip and diff name.
April 3, 2009 at 1:59 am
C:\> nslookup 192.168.0.xx
prompts follwoing message
cannot find server name for adress 192.168.0.yy: (which is address of primary domain) non-existent server
server: unknown
ip adress: 192.168.0.yy
cannot find server 192.168.0.xx non-exesitent server
Please note - cannot connect to the sql only from my PC. other PCs are able to connect to A0002. My PC is running Windows 2003 with SP2 and SQL 2000 with SP4
July 21, 2014 at 12:18 am
I had a similar problem while accessing SQL 2000. On the server I could login through IP but not through name. While trying many things I added a full stop (.) at the end of the name and it worked.
Now I can login from remote machine using 'server_ name' but at the local computer machine I can login using 'server_name.' Perhaps length of the server name could be an issue as it was only four characters in length.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply