Windows Server - Restricting access to internal hosts
Asked By Dugg80
12-Nov-09 07:16 AM
Restricting access to internal hosts
hi all!
i have a problem which i hope you can help me with. please see image located
here:
http://img208.imageshack.us/img208/5421/networkq.jpg
as you can see i connected a router with the company network and which
routes to a gateway connected to the internet. everything is working ok and
there is full connectivity throughout. my problem is that users which are
connecting to the internet via the router are able to access the internal
workstations. is there a way how i could still allow internet access to the
machines connected to the router but disallow them access to the internal
workstations?
thanks!
Firewall
(1)
Connectivity
(1)
Img208
(1)
Rahisuddin Shah replied to Dugg80
I think you need to configure your Router ACLs.
or Firewall can restrict access to workstation segment.
thanks
rahisuddin shah
CEICW fails at Firewall Windows Server SBS 2003 premium ISA 2004 won't connect OWA or RWW and when I run CEICW the firewall setup fails. Everything has been working fine for 6 months. Nothing new installed other then updates. icwlog.txt: 3 / 13 / 2009 12:29 AM Firewall Rule: SBS DHCP Client Cannot find the firewall rule, ignoring the error Firewall Rule: SBS HTTP 80 Out CustomFilter Cannot find the firewall rule, ignoring the error Firewall Rule: SBS FTP 20 In CustomFilter Cannot find the firewall rule, ignoring the error Firewall Rule: SBS FTP 20 Out CustomFilter Cannot find the firewall
Which parts need to be opened thru a firewall [running windows firewall on Windows Server Which parts need to be opened thru a firewall [running windows firewall on server] to enable active directory and SQL server? Thanks Windows Server Networking Discussions ThanksUnless 1) DCF (1) DDB (1) EC (1) EE (1) Firewall (1) Protected (1) Security (1) Unless you have a security expert handy, I would recommend that you just turn the firewall off. There are so many things need to be changed that the chances of getting are protected when you are not. keywords: Which, parts, need, to, be, opened, thru, a, firewall, [running, windows, firewall, on description: Which parts need to be opened thru a firewall [running windows firewall on
Server 2008 with Hyper-V - domain controller - Firewall GUI's show firewall ON, but netsh reports firewall OFF Windows Server I've worked with the Windows Firewall since it was introduced in Windows XP SP2 and Windows 2008 since it went to I have at home for testing etc.). If I run the Start, Administrative Tools, Windows Firewall with Advanced Security it tells me: For your security, some settings are controlled by Group Policy Domain Profile is Active Windows Firewall is on. Inbound connections that do not match a rule are blocked Outbound connections that do not match a a rule are allowed If I run Control Panel, Windows Firewall, it tells me: For your security, some settings are controlled by Group Policy Windows Firewall is on. Inbound connections that do not have an exception are blocked. Display a notification
Windows Firewall Windows Server We have an SBS 2003 Premium with ISA2004 and Symantec Client Security. All have Windows XP SP2. My question is what should I be using for the users firewall. It appears there are (3) choices. Symantec Client Firewall, Windows Firewall and ISA Firewall. What is the best way to proceed? We use Symantec Client Security for our Virus Protection as well. By the way, if you try and turn off the WIndows Firewall at the clients, the option is grayed out. Says something about being controlled by group policy. Windows Server SBS Discussions Windows XP (1) YahooMail (1) FWs (1) Symantec (1) Firewall (1) Kalugin (1) A698D2F5CB7B (1) B903368863FA (1) I recommend using ISA for the network and Windows Firewall for the client PCs. I would not use a 3rd party firewall without first disabling