I don't know if you'll find what's wrong with a packet sniffer, but you may well already have tcpdump installed. The latest RH 7.1 update is tcpdump-3.6.2-11.7.1.0.i386.rpm
On Fri, 1 Nov 2002, Kevin Weslowski wrote: > Hi again, > > I guess a more useful capture would be from the defective machine's end, > right? I think I'll install some packet sniffer on the redhat box and > trap the packets received when I try to connect...will that help? > > Is there a packet sniffer already installed with redhat 7.1? > > Kevin > > Kevin Weslowski wrote: > > > Hi guys, > > > > for those of you who can debug based on packets send/received...I've > > used Iris' Trial Network analyzer to trap the packets sent/received > > during the ftp/ssh attempted sessions and I've attached them... let me > > know if anyone knows how to decipher them and what they mean...thanks. > > > > Kevin > > > > Kevin Weslowski wrote: > > > > > Thanks Steven, > > > > > > actually I don't have a domain name...I always use the IP for SSH or > > > within a web browser, and for everything pertaining to that box...so > > > there's no way it could be a DNS timeout, I think...right? > > > > > > Kevin > > > > > > "Steven J. Yellin" wrote: > > > > > > > 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
