Setting the modem to "Bridged" mode and then having the router log in resolved the issue. I'm still not convinced my old router was "bad," more likely somehow my old modem got taken out of "bridged" mode. Oh, well... I'd been wanting wireless for awhile anyway. :-)
-----Original Message----- From: Angus Scott-Fleming [mailto:[email protected]] Sent: Thursday, March 25, 2010 2:22 AM To: NT System Admin Issues Subject: Re: Internet issues (RANT) On 24 Mar 2010 at 10:34, John Aldrich wrote: > > It´s not so much the PPPoE as it is the switch from a routeable to a > non-routeable IP, unless that´s something in the default configs of the > modem (which may be the case, as I saw some info from my ISP on how to > reconfigure your modem...but I don´t know if it´s applicable to my modem or > not.) Can you set the modem up with a "DMZ" whereby all the incoming traffic gets passed through to one IP -- your PC? One of my clients had to do something like this when their in-house IT guy replaced the modem and didn't know how to set it into bridged mode. He was able to set the modem to pass all the traffic to the internal firewall, which effectively works the same. The new double-NAT setup (Internet <-> aa.bb.cc.dd modem 192.168.1.1 <-> 192.168.1.2 firewall 10.55.0.x <-> LAN) hasn't bitten them yet. -- Angus Scott-Fleming GeoApps, Tucson, Arizona 1-520-290-5038 Security Blog: http://geoapps.com/ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
