[THIN] Re: Timeout
- From: Fred Pabia <FPabia@xxxxxxxxxxxxxxxxxxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Fri, 25 Jul 2003 08:26:58 -0600
I can ping the DNS Server using it's IP address.
-----Original Message-----
From: Braebaum, Neil [mailto:Neil.Braebaum@xxxxxxxxxxxxxxxxx]
Sent: Friday, July 25, 2003 2:33 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Timeout
Can you simply ping the IP address of your DNS server?
Sounds like some fundamental connectivity may be broken (routing?).
Neil
> -----Original Message-----
> From: Fred Pabia [mailto:FPabia@xxxxxxxxxxxxxxxxxxxxxxxx]
> Sent: 24 July 2003 18:08
> To: 'thin@xxxxxxxxxxxxx'
> Subject: [THIN] Re: Timeout
>
> Tried and I still get the timeout error. Yes, 10.1.0.2 is the
> IP address of our primary DNS Server/DC. On my PC,
> 10.1.100.x, I can do an nslookup to DC with no problems. The
> XPe server is on 203.139.1.x and goes through a firewall.
> Anything I should be aware of here? Thanks.
>
> -----Original Message-----
> From: Ryan Lambert [mailto:rlambert@xxxxxxxxxxxxxxx]
> Sent: Thursday, July 24, 2003 10:52 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Timeout
>
>
> Try nslookup with the format:
>
> Nslookup <IP to look up> <IP of DNS Server besides DC>
>
> That should at least give you some output.
>
> Is 10.1.0.2 the IP address of your primary DNS Server/DC?
>
> Sounds like the DNS client on the MF Server or the DNS Server
> on the DC itself isn't working. I'd restart the service on
> each and try.
>
> -----Original Message-----
> From: Fred Pabia [mailto:FPabia@xxxxxxxxxxxxxxxxxxxxxxxx]
> Sent: Thursday, July 24, 2003 12:35 PM
> To: 'thin@xxxxxxxxxxxxx'
> Subject: [THIN] Re: Timeout
>
> We had to manually create the reverse lookup zones and I
> can't use set debug because I just enter nslookup <return>
> and I get the timeout message. Please keep it coming guys. Thanks.
>
> -----Original Message-----
> From: Braebaum, Neil [mailto:Neil.Braebaum@xxxxxxxxxxxxxxxxx]
> Sent: Thursday, July 24, 2003 10:33 AM
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Timeout
>
>
> Automatically creating reverse lookup zones? Can't remember
> if it creates one for the DNS servers current subnet - but
> even so... it'd be a neat trick if it could do it for all the
> subnets you'd likely require.
>
> At this point, nslookup is merely trying to provide the name
> of the DNS server configured (ie it's IP address) - which
> implies either the default for AD zones is not even to create
> a "default" reverse lookup zone for this DNS server's current
> subnet (as I said, it's been a while, and I can't remember),
> and one hasn't been created manually - or it's not an AD
> integrated zone, and one hasn't been created manually, or
> it's a broken reverse lookup zone.
>
> In any of the cases, it's slightly distractionary, anyways,
> as merely not being able to do a reverse lookup, doesn't
> necessarily mean that a forward lookup would fail.
>
> Likely there's more than one thing wrong, here. set debug is
> your friend.
>
> Neil
>
> > -----Original Message-----
> > From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]
> > Sent: 24 July 2003 17:27
> > To: thin@xxxxxxxxxxxxx
> > Subject: [THIN] Re: Timeout
> >
> > That is true...
> >
> > I thought AD Integrated automatically created your reverse
> > lookup zones for you.
> >
> > Though there I go assuming he is even using AD integrated zones.
> >
> > -----Original Message-----
> > From: Braebaum, Neil [mailto:Neil.Braebaum@xxxxxxxxxxxxxxxxx]
> > Sent: Thursday, July 24, 2003 12:22 PM
> > To: thin@xxxxxxxxxxxxx
> > Subject: [THIN] Re: Timeout
> >
> > Well the "can't find server name for IP address" message is
> > referring to DNS being unable to do a reverse lookup for
> > 10.1.0.2 - which I take it is your DNS server?
> >
> > This is suggesting you haven't got your reverse lookup zones
> > configured.
> >
> > But in itself, isn't necessarily going to cause you a problem
> > with forward lookups.
> >
> > Do an nslookup in interactive mode (ie no argument to it), do
> > set debug, then enter the hostname again and post your results.
> >
> > Neil
> >
> > > -----Original Message-----
> > > From: Fred Pabia [mailto:FPabia@xxxxxxxxxxxxxxxxxxxxxxxx]
> > > Sent: 24 July 2003 17:05
> > > To: 'thin@xxxxxxxxxxxxx'
> > > Subject: [THIN] Re: Timeout
> > >
> > >
> > > 'DNS request timed out. Timeout was 2 seconds. ***can't
> find server
> > > name for IP address 10.1.0.2: Timed out'
> > >
> > > The primary DNS server is our DC which is a W2K Server with SP3.
> > >
> > > Thanks.
> > >
> > > -----Original Message-----
> > > From: Ryan Lambert [mailto:rlambert@xxxxxxxxxxxxxxx]
> > > Sent: Thursday, July 24, 2003 10:04 AM
> > > To: thin@xxxxxxxxxxxxx
> > > Subject: [THIN] Re: Timeout
> > >
> > >
> > > Post the output of your nslookup command here.
> > >
> > > Also what is your primary DNS server?
> > >
> > > -----Original Message-----
> > > From: Fred Pabia [mailto:FPabia@xxxxxxxxxxxxxxxxxxxxxxxx]
> > > Sent: Thursday, July 24, 2003 11:53 AM
> > > To: Thin Forum (E-mail)
> > > Subject: [THIN] Timeout
> > >
> > > I have a Metaframe XPe Server FR2 which is a member of a
> W2K Domain
> > > - AD & DNS on same box. Doing a nslookup for the domain always
> > > answers back with DNS request timed out. Time out was 2
> seconds etc
> > > etc etc Any ideas on why this would happen at all? Thanks.
***********************************************
This e-mail and its attachments are confidential
and are intended for the above named recipient
only. If this has come to you in error, please
notify the sender immediately and delete this
e-mail from your system.
You must take no action based on this, nor must
you copy or disclose it or any part of its contents
to any person or organisation.
Statements and opinions contained in this email may
not necessarily represent those of Littlewoods.
Please note that e-mail communications may be monitored.
The registered office of Littlewoods Limited and its
subsidiaries is 100 Old Hall Street, Liverpool, L70 1AB.
Registered number of Littlewoods Limited is 262152.
************************************************
********************************************************
This weeks sponsor - IDP ServerBoss
Restrict, Manage and Control Access to your applications
and other valuable Citrix, Windows NT, 2000
and 2003 Server Resources
http://www.serverboss.com/default.asp?partner=thethin
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
********************************************************
This weeks sponsor - IDP ServerBoss
Restrict, Manage and Control Access to your applications
and other valuable Citrix, Windows NT, 2000
and 2003 Server Resources
http://www.serverboss.com/default.asp?partner=thethin
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
Other related posts:
