July 14, 2005 at 11:15 am
I've brought up a new SQL Server (2000) running on a 2003 Server platform. All seemed normal during the install and patch processes. The problem is that from a client machine on the network, when creating a DSN I don't see the SQL server name as available in the server selection drop down. If I type in the name my DSN does not work. If I type in the IP Address of the server the DSN works. Any help/suggestions would be appreciated.
July 14, 2005 at 12:08 pm
From a command prompt, can you resolve the name. In other words if you type:
nslookup
Do you get back an IP address?
K. Brian Kelley
@kbriankelley
July 14, 2005 at 12:09 pm
Hello,
It is a name resolution issue. You say it is a new server. It may be one of the following:
- DNS server that resolves the name into IP address does not have a record for your server yet. Contact your domain admin.
- The server is in a different domain from the client. Use fully qualified name like servername.domainname.companyname.com
I would open the command prompt Start-Run-cmd
and test the following 2 commands:
ping myservername
ping myservername.domainname.companyname.com
Yelena
Regards,Yelena Varsha
July 14, 2005 at 12:21 pm
I just want to add that in Server Network Utility of SQL Server on General tab in selected protocols if you click TCP/IP and click Properties there is a Hide Server checkbox. It may also be a reson why the server is not showing in the list. You should be able to connect anyway, it would not just advertise itself on the network.
In my experience mostly servers on the same subnet are in the list and those that are specified in Client Network Utility on the client (don't mix it with Server Network Utility)
Let us know if you need more help
Yelena
Regards,Yelena Varsha
July 14, 2005 at 12:36 pm
If this was the case, though, SQL Server would go to listening on port 2433 instead of 1433. In that case he'd have to specify the IP and port in order to make a connection.
K. Brian Kelley
@kbriankelley
July 14, 2005 at 1:11 pm
Hi,
Listen to Brian, he is totally correct. More reasons it does not work.
What are you using by the way on the client? Named Pipes still may work if the name resolution is OK on DNS box. What is your default protocol ?
Yelena
Regards,Yelena Varsha
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply