The first thing i noticed is that I no longer can copy/paste the complete license key, but have to copy/paste one and one group of characters into the install wizard. I liked it better the old way.

Looking forward to see if there is some big changes, I was after all already very happy whit the BETA version

I found a article at Microsoft: “Internet firewalls can prevent browsing and file sharing” and there i found all the ports that where used for file sharing:

• Microsoft file sharing SMB: User Datagram Protocol (UDP) ports from 135 through 139 and Transmission Control Protocol (TCP) ports from 135 through 139.
• Direct-hosted SMB traffic without a network basic input/output system (NetBIOS): port 445 (TCP and UPD).

And after reading that i started looking at the F-Secure Firewall services again and found two services. “SMB over TCP/IP (TCP)” and “SMB over TCP/IP (UDP)” witch in fact does the same as i did yesterday by opening port 445.

So, I’m sorry to have blamed F-Secure before checking better but after finding the “Windows file sharing and network printers” service i just didn’t think about looking for an SMB service, sorry, my bad.

On the other side, i think that thees services should have another name because a normal user probably don’t know what SMB is, but might still want to share files. So a tips to -F-Secure this time is to give this services a better name.

The F-Secure service named “Windows file sharing and network printers” only open TCP port 139 while Windows file sharing wants to use TCP port 445. So I created a new service for port 445 and added it to the rule and then file sharing worked fine…

I think TCP port 445 should be added to the “Windows file sharing and network printers” service.

Update:

I was wrong. Sorry, my bad.

I have tested with different profiles and it has not worked on any of them. But a few days ago i noticed that if i use the office firewall profile I’m not able to open for file sharing because it’s denied in a later rule by default, and that’s a rule I cannot change. So if I allow file sharing in a rule i create myself, it will just be denied by the default rule afterwords.

Shouldn’t I be able to choose for myself if I want to share my files in an office environment? I want to be able to change that rule, or even remove it…

My new testlab is a HP ProLiant ML110 with Windows Server 2008 x64

On this server I run the Hyper-V service, and on top of the Hyper-V I have the following clients:

• Windows Vista enterprise x64
• Windows Vista enterprise x86
• Windows 7 professional x64
• Windows 7 professional x86
• Windows XP professional x86

I just found out that the File sharing rule don’t work at all. I previously stated i use F-Secure Client Security 9.0 BETA on a Windows 7 x64 RTM client.

The RDP Rule is still working, and i have created a new rule for a random port to test and that worked to.
So it’s just the file sharing rule for Windows File sharing that don’t work.

How i created the rule:

• Add new rule
• Name: “File sharing”
• Allow
• All IP addresses
• Service: “Windows file sharing and network printers”
• Both ways
• No alert
• Finish

Can there be something wrong with the “Windows file sharing and network printers” service?

Until now i have only experienced one little problem whit the Firewall.
I was going to open for RDP (Remote desktop protocol), and Windows file sharing. Created one rule for the RDP and it worked fine, and then I created the file sharing rule and nothing happens. Waited for about 10 minutes, and still nothing. So i had to reboot my system to get the the rule to work. I guess it’s not suppose to be that way.

I have only tested this on one client yet, but i will do some more testing during the week!

Update:
Please read the post “Correction – Firewall issue“

Still much more testing to do, but at first glance it looks really good!