Q: configuring home network after blaster worm recovery

[Gary Ford]

I have a home network with a Windows 2000 Professional machine
connected to the Internet via DirecWay/Earthlink. The other machines on
the home network are running RedHat Linux 7.3, Mac OS 10.2, and Mac OS
9.1. Windows "Internet Connection Sharing" works, allowing all the
machines to get to the Internet.

However, after installing the recent Win2000 service packs and security
patches related to the blaster worm, the other machines on the network
can no longer see each other. In particular, the Mac OS X machine runs
a web server for the home network, and the Linux and Win2000 machines
can no longer connect to that server. Watching the lights on the
DirecWay modems suggests that the Win2000 machine is trying to send the
192.168.0.x addresses out for DNS look-up.

Suggestions would be appreciated on how to configure any or all of
these machines to restore the connectivity. Please respond to this
group. Thanks.

Gary Ford
Plaid Flannel Software

 

[The Gang@Triple H Computers]

After 2 hrs "phone time" to DirecWay's support we added these to a customers
NIC (ICS machine) Preferred DNS 198.77.116.8 & 198.77.116.12.. They were in
a similar
situation..

 

[Jack Seredyniecki]

Are the machines *pingable* by IP address?

 

[Stephen M. Adams]

I have a home network with a Windows 2000 Professional machine
connected to the Internet via DirecWay/Earthlink. The other machines on
the home network are running RedHat Linux 7.3, Mac OS 10.2, and Mac OS
9.1. Windows "Internet Connection Sharing" works, allowing all the
machines to get to the Internet.

However, after installing the recent Win2000 service packs and security
patches related to the blaster worm, the other machines on the network
can no longer see each other. In particular, the Mac OS X machine runs
a web server for the home network, and the Linux and Win2000 machines
can no longer connect to that server. Watching the lights on the
DirecWay modems suggests that the Win2000 machine is trying to send the
192.168.0.x addresses out for DNS look-up.

If this is the case, create host files on the various machines. That's
how I solved naming conventions. Also, ensure that the Windows box is
not using proxy for local net connections.

-Stephen

 

[Gary Ford]

The problem was HTTP proxy settings on the various machines. Although
DirecWay recommends that ICS client machines use HTTP proxy
192.168.0.1:85 (which works for browsing the external web), that
destroys HTTP access on the LAN.

Thanks to all who responded.

Gary Ford
Plaid Flannel Software