[NTLUG:Discuss] More @home issues....

lee@brave.com lee at brave.com
Wed Jan 24 13:43:35 CST 2001


how timely to have an @home discussion...  sorry to change subject, but
somehow i think this may be related.

i have a linux box router/firewall arrangement, with masq'd boxes on an
internal lan.  everything works great except i get a "no route to host"
error when trying to reach their news server, from either the firewall box
or any pc on my network, either linux, native windows or vmware'd windows.

*except* if i plug a native windows box into the cable modem, i can reach
their news server; this is the only arrangement that seems to work -- and
other than this strange anomaly, everything else is unchanged and seems to
be working flawlessly.

any explaination from you networking gurus?  or how would i go about
finding out why the news server won't respond unless the cable modem is
connected directly to a windoze box?

baffled,

-- lee

On Wed, 24 Jan 2001, MadHat wrote:

> I run AT&T @home and have no such issues.  I do have to reset the cable 
> modem when I change machines or NICs due to ARP retention, but nothing with 
> the name.
> 
> I personally would not set up SAMBA on @home.  It is asking for trouble, 
> security wise.
> 
> 





More information about the Discuss mailing list