cancel
Showing results for 
Search instead for 
Did you mean: 

Problems configuring CIFS on Windows

sscbrian
Champ on-the-rise
Champ on-the-rise
I've configured the Windows Advanced Firewall to reject 445/tcp completely.  My understanding is that will force CIFS connections down to the low ports where Alfresco can capture them.  However, when I try to connect I get a failure to connect to the server at all.  Looking for any help/experience that Windows users might have to share.  Here's my current configuration (I've read a number of blogs and docs with all kinds of options that don't seem to do anything.  Currently stripped down to this which still doesn't do anything):


cifs.enabled=true
cifs.serverName=docs.domain.com
cifs.domain=domain.com
cifs.sessionTimeout=500
cifs.ipv6.enabled=true
cifs.WINS.autoDetectEnabled=true
5 REPLIES 5

mrogers
Star Contributor
Star Contributor
Port 445 is for the tcp implementation for CIFS.    139 and 137 are for NetBios which you probably want to avoid if at all possible. 

sscbrian
Champ on-the-rise
Champ on-the-rise
So, should I unblock 445/tcp on the firewall for Alfresco?

mrogers
Star Contributor
Star Contributor
Yes.  Why do you think blocking it is a good idea?

sscbrian
Champ on-the-rise
Champ on-the-rise
The blog post I read about setting up CIFS on Windows said I had to do that to force it to the low ports.  Something about Windows not allowing Alfresco to use port 445.  Is that information out of date now?

mrogers
Star Contributor
Star Contributor
There can be conflict with windows' own cifs implementation.     And sometimes windows may be lazy and not bother to resolve the server by the net bios name.   ( the one with the training A ).    

It's difficult to comment on a blog without more details.