Re: VPN/PPOE/RWW Questions/Security

From: R (12345_at_12345.com)
Date: 03/23/05 

Date: Wed, 23 Mar 2005 09:24:01 -0600

"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
wrote in message news:OZkq4G2LFHA.3812@TK2MSFTNGP10.phx.gbl...
> The attitude for many is that Linksys' quality is going downhill.

That wouldn't happen to have anything to do with Cisco (Linksys' new owner)
encouraging "upgrading" to _real_ Cisco gear?

>
> What ports do you have open on that router?
>
> And what kind of ping/traffic are you seeing? Ensure that you have
> strong passwords on all accounts.
>
> Paul wrote:
> > I have a few questions that are pretty much related so I'm putting them
> > together in this one post.
> >
> > I am running SBS 2003 Standard with one nic and a hardware
firewall/router.
> > My LAN (10 pc's) uses static ip's provided by the ISP and I've set up
one to
> > one mapping on the firewall.
> >
> > VPN works ok except for an issue with one remote user that uses
DSL/PPPOE at
> > home. He can connect to the SBS server fine but when he disconnects he
says
> > that his home LAN becomes inoperable. He can't surf the internet and has
to
> > restart the modem to get his LAN back on line. He is behind a Linksys
> > firewall. I'm guessing that he is having IP issues after using the VPN.
Is
> > there some setting on his Linksys or on the SBS server I should be
adjusting?
> >
> > On that note, I've noticed when I connect from home through VPN that the
> > public IP assigned to me has been one that I thought was already in use.
Is
> > this possible/should I map or assign more public IP's for the LAN?
> >
> > Finally, I have seen port 443 probed to death on my firewall logs for
RWW.
> > I've seen only one or two articles addressing RWW's inherent security (I
> > think Marina provided a link in another thread) but I'm looking for more
> > feedback. Assuming my SBS is patched and I have strong password
policies, how
> > vulnerable am I with port 443 out there in the open.
> >
> > Thanks in advance.

Relevant Pages

  • Re: Just an interesting note.
    ... There was no NAT at the Cisco rtr, ... you assign a block of IP's on the outside port of the Cisco ... Linksys LAN side IP address. ...
    (alt.internet.wireless)
  • Re: Just an interesting note.
    ... with some protocols that need port forwarding from the internet ... There was no NAT at the Cisco rtr, ... you assign a block of IP's on the outside port of the Cisco ... Linksys LAN side IP address. ...
    (alt.internet.wireless)
  • RE: SSL on multiple sites in a virtually hosted WinServer 2003
    ... You cannot use the Linksys routers. ... You have to map the public IP's via NAT to the Private ones Use the Cisco ... my ISP and its address is the public gateway. ... This setup works fine for only one SSL enabled site. ...
    (microsoft.public.windows.server.networking)
  • Re: Just an interesting note.
    ... with some protocols that need port forwarding from the internet ... There was no NAT at the Cisco rtr, only the actual IP routing functions. ... Linksys LAN side IP address. ...
    (alt.internet.wireless)
  • Re: Cisco 1300 series wireless access point/bridge Vs Linksys WAP54GPE Access Point Anyone know
    ... I think i'm mostly concerned with security issues of using a Linksys ... Vs Cisco, but from what some have said, it doesn't seem to be too much ... It's only when they go across the wire that it's slow. ...
    (comp.dcom.sys.cisco)
Loading