RRAS as IIS basic fireawll (1 NIC)

•

What is DaniWeb IT Discussion Community?

You're currently browsing the Windows Servers and IIS section within the Tech Talk category of DaniWeb, a massive community of 456,480 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 2,809 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.

Join our community!

Please support our Windows Servers and IIS advertiser: Programming Forums

Thread Tools Display Modes

Views: 665 | Replies: 1 | Solved

•

Join Date: Feb 2008

Posts: 42

Reputation: bbqchickenrobot is an unknown quantity at this point

Rep Power: 0

Solved Threads: 2

bbqchickenrobot bbqchickenrobot is offline

Offline

Light Poster

RRAS as IIS basic fireawll (1 NIC)

Apr 1st, 2008

Hi all, I have enabled and configured RRAS on my Windows 2003 server (IIS) machine to perform basic firewalling. I have enabled it and all works from the outside world, however, I cannot connect to the outside world on the machine. But the outside world (web users, FTP, etc...) can connect to me.

I have a single NIC with a public IP only. I haven't used any Internal network IPs - I configured RRAS to user services but pointed them to the public IP. It works, for people connecting... web users can browse the server, but when I'm at the terminal, I am unable to browse the internet or connect outbound to any other network using tcp/ip.

outbound tcp/ip hosts aren't pingable, tracert-able, nslookup won't work (can't find DNS server), etc... I enabled IP filtering with rules that allowed DNS (TCP/UPD port 53) and enabled all outbound traffic... not really sure what I am doing incorrectly.

Any help would be appreciated.

•