Application Connection Issue - DNS Issue

[Dave]

Archived from groups: microsoft.public.win2000.dns (More info?)

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.

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:CC13D53F-D9CA-4FCD-B148-57036E9F6A9E@microsoft.com,
Dave <Dave@discussions.microsoft.com> asked for help and I offered my
suggestions below:
> 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.

Some questions:

1. Cold serer? You mean ColdFusion?

2. Are you configuring your machines with your ISP's DNS? Remove them if the
case and configure a forwarder. If the option is grayed out, delete the Root
zone and try again. THis article shows how:
http://support.microsoft.com/?id=300202

3. Is this an NT or Win2k domain? My assumption is its an AD domain, hence
the long logon times due to the DNS misconfiguration.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================

 

[Dave]

Archived from groups: microsoft.public.win2000.dns (More info?)

1. Cold Server is a optical storage server using Legato
software frontend. (application extender)

2. DNS has no root zone and is set for forwarders

3. the logon is not at network logon that functions
normally with no delay. the delay is when you open
application extender and it makes its initial connection
to SQL. after its connected it operates at normal speed
when performing queries.

4. yes it is a w2k doamin. all win 2000 pro and xp pro
work fine it is only the nt 4 workstations.

thanks
dave
>-----Original Message-----
>In news:CC13D53F-D9CA-4FCD-B148-
57036E9F6A9E@microsoft.com,
>Dave <Dave@discussions.microsoft.com> asked for help and
I offered my
>suggestions below:
>> 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.
>
>Some questions:
>
>1. Cold serer? You mean ColdFusion?
>
>2. Are you configuring your machines with your ISP's DNS?
Remove them if the
>case and configure a forwarder. If the option is grayed
out, delete the Root
>zone and try again. THis article shows how:
>http://support.microsoft.com/?id=300202
>
>3. Is this an NT or Win2k domain? My assumption is its an
AD domain, hence
>the long logon times due to the DNS misconfiguration.
>
>--
>Regards,
>Ace
>
>Please direct all replies ONLY to the Microsoft public
newsgroups
>so all can benefit.
>
>This posting is provided "AS-IS" with no warranties or
guarantees
>and confers no rights.
>
>Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I,
MCT, MVP
>Microsoft Windows MVP - Active Directory
>
>HAM AND EGGS: A day's work for a chicken;
>A lifetime commitment for a pig.
>--
>=================================
>
>
>.
>

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:CC13D53F-D9CA-4FCD-B148-57036E9F6A9E@microsoft.com,
Dave <Dave@discussions.microsoft.com> posted a question
Then Kevin replied below:
> 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.

Can you give us an example of the nslookup output?

Have you defined a domain suffix search list on the NT4? IIRC NT4 doesn't do
this automatically, you have to manually add domain suffix search list.


--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
--
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your
issue. To respond directly to me remove the nospam. from my
email. ==========================================
http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:2bb1d01c46810$816ff4e0$a301280a@phx.gbl,
dave <dave@discussions.microsoft.com> asked for help and I offered my
suggestions below:
> 1. Cold Server is a optical storage server using Legato
> software frontend. (application extender)
>
> 2. DNS has no root zone and is set for forwarders
>
> 3. the logon is not at network logon that functions
> normally with no delay. the delay is when you open
> application extender and it makes its initial connection
> to SQL. after its connected it operates at normal speed
> when performing queries.
>
> 4. yes it is a w2k doamin. all win 2000 pro and xp pro
> work fine it is only the nt 4 workstations.
>
> thanks
> dave

Thanks for the additional info. If its just the NT4 machines, have you
looked into WINS to make the resolution process more efficient? Reason I say
this is I am *assuming* that you are connecting to your cold server by
single name? Therefore, W2k and XP will append its suffix to it and perform
a hostname resolution (DNS) whereas NT4 will not and will use NetBIOS as the
default means. You could also on the NT4 machine check off to use DNS for
hostname resolution and insure the suffix matches the zone where the Cold
resource is under.

You can test this by simply creating an lmhosts entry for the Cold server on
the NT4 machine and see if it speeds up.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================