Hi again, well, maybe it is some sort of DNS error...well, SSH/http started working last night again, but not ftp...ftp started working this morning...
I did a capture of an unsuccessful ftp session last night and there were several packets sent to my ISP's DNS server, querying about 192.168.1.1 Why would it try to resolve an IP, and an internal network IP at that? This morning I also captured a successful ftp session and there are only 2 packets re: DNS...1 from my machine and a reply from the DNS server... I don't know what this means, but if someone can help, I'd appreciate it... thanks, Kevin 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 > > _______________________________________________ > Seawolf-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/seawolf-list
ftp_session.cap
Description: Binary data
