After a devastating hit from W32 worms to one of my home
PCs as I was trying to activate a new WinXp upgrade
online, I purchased a Linksys router for the DSL
connection (can't rely on software firewall all the
time). Setup to my WinXP webserver and WinXP main PC was
seamless. I continue to run ZoneAlarm on the webserver
and Norton Internet Security on the other. Both have
Norton Antivirus active. Network mapping of the
webserver's "Shared Docs" also went well (port forwarding
of the webserver makes this smooth) and both afford 100
Mps transfer via the router.
I then decided to add a remote WinXP PC (also running
Norton Internet Security/Anti-Virus) that is dedicated to
another task and a PS2 wirelessly. I did this with a MN-
700 base (802.11g), MN-710 adapter (802.11g), and Netgear
Game Adapter (802.11b). The MN-700 runs as a sub-LAN
through the Linksys router - being assigned an dynamic IP
from the Linksys. The MN-700, in turn, acts as a DHCP
server for the sub-LAN ( ie. the PS2 and the remote PC).
The set-up to the remote PC went smoothly. I even mapped
the "Shared Docs" of my webserver from the main Linksys
LAN to this PC on the wireless sub-LAN without a hitch.
The PS2 was problematic. Not so much from a Microsoft
point-of-view, but from a Netgear documentation point-of-
view. I finally figured out that with WEP encryption,
that after Game Adapter Setup I had to flip channels to
what Netgear labels "P1". After that, PS2 was online!
This is my story. It's true. It took a week to
understand the various protocol's and the idioms of
various components, but it's all cool. Hardware firalls,
software firewalls, wired, wireless, Microsoft, non-
Microsoft...communicating harmoniously.
The End
|
Similar Threads
Linear Mode
