FYI In regard to point 9 below. When you use a regular "server name" instead
of a FLQN name you cause the JDBC server system to do the following:
First it uses the unc service...
check the host file for that string to resolve (no dice)
check dns (also no dice)
.....move to rnc service (windows locator - basically a handoff to
windows)....
check lmhosts file (if enabled and configured to do so)...
check active directory created flqn on the nearest dc if you are on a domain
([EMAIL PROTECTED])
check Active dir on the master domain controller if nearest dc fails..
try to resolve the name using windows locator broadcasting....
It's a lot of hoops just for a friendlier naming scheme. Mostly, you just
don't want windows to have to do this work for you. Windows networking is
more dns based, but it still has a locator service with a fairly complicated
heirarchy of resolution attempts. Instead, you want the JDBC service to
bypass the application layer and get that name resolved prior to it arriving
at the windows locator service. Simply ask yourself - "how is the server
going to resolve this name".
Mark Minasi's "mastering windows server 200x" books have some great
information on how windows goes about this process.
Mark A. Kruger, CFG, MSCE
www.cfwebtools.com
www.necfug.com
http://blog.mxconsulting.com
-----Original Message-----
From: Bill Grover [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 31, 2004 9:34 AM
To: CF-Talk
Subject: RE: 100% CPU
Thanks for the response. I'll work on this list and see if it doesn't
help. Here is some responses to a few of your points.
1. On the server in question we don't have any access. Just SQL Server
2. I'll try the updated drivers.
8. SQL is not on the web server. Both boxes are separate servers.
9. Our names are not FQDN but are not IP addresses either. We just use
the server name (sql-server). I'll play with the host file.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
