UnaBonger Posted May 8, 2003 Share Posted May 8, 2003 hah the problem is you may be able to hit the router but after that the ip is setup as vpn and there is nothing open that you can attack :p Then you do have a firewal... :blink: Link to comment Share on other sites More sharing options...
LaraBoft Posted May 8, 2003 Share Posted May 8, 2003 This is confusing.... Link to comment Share on other sites More sharing options...
eye_see_you Posted May 8, 2003 Author Share Posted May 8, 2003 no not a firewall just using vpn ip address after the router thats not really a firewall Link to comment Share on other sites More sharing options...
Joel Posted May 8, 2003 Share Posted May 8, 2003 no not a firewall just using vpn ip address after the router thats not really a firewall http://www.webopedia.com/TERM/f/firewall.html Link to comment Share on other sites More sharing options...
Steven Posted May 8, 2003 Share Posted May 8, 2003 http://www.webopedia.com/TERM/f/firewall.html lol silly_walk. if my router isn't a firewall then i dunno what it is :laugh: Link to comment Share on other sites More sharing options...
Joel Posted May 8, 2003 Share Posted May 8, 2003 lol silly_walk.if my router isn't a firewall then i dunno what it is :laugh: Apparently, this concept is lost on some of us ;) Link to comment Share on other sites More sharing options...
eye_see_you Posted May 8, 2003 Author Share Posted May 8, 2003 well ok I did not think about it but a router is like a firewall but nothing that we can configure on our end . I totally forgot about what a router does lol ..... *Doh Link to comment Share on other sites More sharing options...
UnaBonger Posted May 8, 2003 Share Posted May 8, 2003 I think to get back on track and help, that the point that was just made is that your network is protected... So, in my opinion running IIS (as long as it's configured properly) shouldn't pose any problems, and by running IIS you can then run SUS... Link to comment Share on other sites More sharing options...
Recommended Posts