Date: Sat, 30 Dec 1995 12:50:24 GMT From: buaas@wireless.wdc.net (Robert A. Buaas) To: questions@freebsd.org Subject: TCP connection prob in 2.1.0-REL Message-ID: <199512301250.MAA28941@wireless.wdc.net>
next in thread | raw e-mail | index | archive | help
Happy New Year everyone!! I've just upgraded a FreeBSD v1.0 system (wireless.net, 198.253.254.1) to 2.1.0-RELEASE. It's fed over a SLIP link from nosc.mil. Pings/DNS queries work fine from everywhere. Telnets/FTPs/POP3s/etc work fine EXCEPT from wireless.wdc.net (204.140.136.28) and n1.wdc.net (204.140.136.18). For example, and FTP from wdc.net displays the text "connected to wireless.net" and hangs. On wireless.net an ftpd process is created, and it disappears when the hung client ftp is killed off manually. Similiarly, telnet and POPs don't work in about the same way. Receiving mail is less clear: received correctly from nosc.mil, ucsd.edu, but not from aol.com, wdc.net. We thought the problem might be a mis-configuration of the DNS on wireless.net, so we killed named and removed wireless.net from /etc/resolv.conf, using only trout.nosc.mil for DNS service. No difference we could tell. We discovered a duplicate name for 198.253.254.1 in trout: wireless.nosc.mil, and this is being deleted. Running FreeBSD v1.0 continues to work fine. Anyone have any suggestions where to look next? Thanks in advance. We want very badly to stay with this new system, but we're effectively offline until we find this problem. best regards/bob
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512301250.MAA28941>