Application connection issue

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Dave - 09 Jul 2004 17:19 GMT

We have an application on are network that use (ODBC for cold application). When we log onto the application the initial connection is very slow and it takes about 30-60 seconds to log on. Once we have logged onto the application, I can browse the data without any delays. It seems that that problem exist only with Windows NT 4.0, and not with Windows 2000 or XP. We are running Active Directory on our network, which resolves DNS. We also have a second DNS zone. Our servers have records in both zones along with associate PTR records. We checked to make sure that the name and IP address of the COLD server are in the DNS tables. We did a NSLOOKUP by IP address and the name and address of the COLD Server reply with the correct network information. If we put in the name of the COLD Server an error messages comes back with a DNS request time out, can’t find COLD Server.

Reply to this Message

Scott Harding - MS MVP - 09 Jul 2004 22:06 GMT

Sort of sounds like a Netbios issue if only the NT4 machines are affected.
Are you using WINS at all? NT4 machines do not use DNS first to resolve
computer/host name and they turn to DNS as a last result after
WINS/broadcast etc. An easy test would be to put a lmhosts file on a NT4
machine with the name of the server(whatever name you put into the ODBC
connection) and reboot or load into cache and see if that helps. This would
be easier than setting up WINS to test. If this helps then you could
implement WINS or just add this lmhosts file to each workstation. Be careful
to save the lmhosts file with no extension.

Signature

Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

> We have an application on are network that use (ODBC for cold application). When we log onto the application the initial connection is

very slow and it takes about 30-60 seconds to log on. Once we have logged
onto the application, I can browse the data without any delays. It seems
that that problem exist only with Windows NT 4.0, and not with Windows 2000
or XP. We are running Active Directory on our network, which resolves DNS.
We also have a second DNS zone. Our servers have records in both zones along
with associate PTR records. We checked to make sure that the name and IP
address of the COLD server are in the DNS tables. We did a NSLOOKUP by IP
address and the name and address of the COLD Server reply with the correct
network information. If we put in the name of the COLD Server an error
messages comes back with a DNS request time out, can't find COLD Server.

Reply to this Message

dave - 12 Jul 2004 18:20 GMT

WE have tried lmhosts didnt help we do have wins running
and all seems fine with it. we can do a net view to server
no delay and once application makes initial connection
then there is no delay only on initail connection.
Dave

>-----Original Message-----
>Sort of sounds like a Netbios issue if only the NT4 machines are affected.
[quoted text clipped - 21 lines]
>
>.

Reply to this Message