On Thu, 31 Oct 2002, Kevin Weslowski wrote:
> Hi John,
>
> my internal network: 192.168.1.x
> the defective machine: 192.168.1.1 and one other machine 192.168.1.2
> Why would it be a DNS timeout from inside the network and not outside?
> How do I check if it's a DNS timeout?
> Thanks,
>
> Kevin
>
One way to check that it's a problem with DNS lookup is to replace
names with IP numbers -- for example, "ssh <username>@24.72.33.63",
and similarly for web browser URL's, as in "http://24.72.33.63";. If
those make rapid connections, but names work poorly or not at all,
then the problem would seem to be with your DNS (or your use of it).
> John Dalbec wrote:
>
> > > Date: Wed, 30 Oct 2002 21:40:17 -0600
> > > From: Kevin Weslowski <[EMAIL PROTECTED]>
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: ftpd and sshd services not responding
> > > Reply-To: [EMAIL PROTECTED]
> > >
> > > Hi Jason,
> > >
> > > I'm getting the feeling this is more and more like a networking issue...
> > >
> > > man am I leading you guys on a wild goose chase...really, I don't mean to!
> > >
> > > I asked a friend to browse to my ip (24.72.33.63) from a web
> > > browser. He said it came up the same speed as any other site. While
> > > still within my internal network, I can't retrieve it faster than
> > > 30-60 seconds...So it seems like anyone else but this machine has no
> > > problems...why me!?
> >
> > Sounds like a DNS timeout. What does your "internal network" look like?
> > John
--
Steven Yellin
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
