ODBC connection fails without fully qualified DNS name

Hi,

I have a Database server (DBserver) that hosts an application (sql 2005 sp3) We have disabled named pipes as part of the requirements.
All the application servers are able to connect to it using TCPIP to the DBserver\instance with no problem except one
One server is unable to connect via odbc unless we do it with the IP address or the fully qualified hostname. (If we enable named pipes on the DB it works as well)
When we ping the DB server it does return the fully qualified name with the suffix, and comparig the network settings on the server we dont see any diffrence.

The application does not allow us to put in th full name....
Seems to be something wrong with the TCPIP
Anyone come across something similar?
neoptoentAsked:
Who is Participating?
 
bbaoIT ConsultantCommented:
does that application server use WINS, rather than DNS, to resolve host names in a higher priority??
0
 
EvilPostItCommented:
This sounds like a IP lookup problem to be honest. From the box that is trying to connect try doing..

ping DBHOSTNAME

Open in new window


If it resolves its the client not the host.
0
 
neoptoentAuthor Commented:
They are both setup to use DNS first
If I ping -a  the dbserver it resolves the correct dns suffix

I also tried removing WINs to see if that helped
0
 
Marten RuneSQL Expert/Infrastructure ArchitectCommented:
How many networks do you have, whats the subnet of the source and target servers (i e the server that cant connect and the sql server)?

Is DNS Suffix added in network settings for the malfunctioning server?

//Regards Marten
0
 
neoptoentAuthor Commented:
Really needed cliconfg to change to get rid of named pipes
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.