I answered my own question. Seems that the SSH server on the NATed box needed to be restarted. Probably because of the new NIC I put it in. (... although it would''ve restarted when I rebooted after the hardware change, so I don''t know. It''s a VShell server on Win2K, if anyone has any insight). - Colin
--On Tuesday, November 05, 2002 10:48 AM -0500 Colin Viebrock <colin@easydns.com> wrote:> I answered my own question. > > Seems that the SSH server on the NATed box needed to be restarted. > Probably because of the new NIC I put it in. > > (... although it would''ve restarted when I rebooted after the hardware > change, so I don''t know. It''s a VShell server on Win2K, if anyone has > any insight).Did you purge the Arp Caches of the other systems on your network (in particular, you firewall''s) when you changed the NIC? -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net
> Did you purge the Arp Caches of the other systems on your network (in > particular, you firewall''s) when you changed the NIC?Not knowingly. (translation: how would I do that?) - Colin
--On Tuesday, November 05, 2002 11:11 AM -0500 Colin Viebrock <colin@easydns.com> wrote:>> Did you purge the Arp Caches of the other systems on your network (in >> particular, you firewall''s) when you changed the NIC? > > > Not knowingly. > > (translation: how would I do that?) >man arp -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net