Windows Firewall doesn't work as advertised: "File and Sharing (SMB-in)" fails to restrict by user, computer or IP.
Tuesday, January 01, 2013 3:40 AM
I'm trying to understand whether I'm the one who's crazy, doing something wrong, or whether Windows Firewall was designed to be broken (and stay that way through Windows Server 2008 R2!)
When I go to Windows Firewall with Advanced Security from the Start Menu and edit the Inbound Rule for "File and Sharing (SMB-in)", the result I am seeking is that I can restrict access by both user and computer.
Upon enabling the rule, and selecting the "Allow the connection if it is secure" option (and nothing else), the firewall obliges by denying any and all attempts by other computers to map or browse files.
When I enter the name of one PC in the Computers tab under the "Allow connections from these computers", again the firewall obliges and the said PC can now browse and map to shares on that server. HOWEVER, now other computers on the network are able to do the same, as long as they have any set of verifiable credentials (like a local user/admin or domain user/admin, etc). Trying to restrict by user or by IP yield almost identical results. Both those who I do and do not want are able to access files on the said server.
My question is this: how is this firewall rule supposed to work? What do we have to do to actually make it accept and reject connections based on the criteria we have provided?
My goal is to only allow SMB access to a user IF they log in from a particular computer or group of computers.
Any help would be GREATLY appreciated!
Friday, January 04, 2013 6:14 PMSo no one has any idea??
Tuesday, January 08, 2013 10:50 PMErrr... anyone??
Saturday, January 12, 2013 3:18 AMSOMEONE's got to know SOMETHING about this problem!! Aren't there any Microsoft developers browsing these forums??
Monday, January 14, 2013 1:39 AM
You may try the MSDN forum:
- Marked As Answer by K_evin ZhuMicrosoft Contingent Staff, Moderator Monday, January 28, 2013 1:46 AM