Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Wikipedia mentions only TCP port 445 (while as far as I can remember ports 137-139 used to be used actively by Windows file sharing).

If I map the 445th TCP port on gateway host "A" to a 445th TCP port of SAMBA server host "B", will Windows XP client host "C" be able to access shared folders on "B" by typing "\ipAddresOfHostA\" in his address bar while being connected with "A" with OpenVPN TCP/IP tunnelling?

PS: No broadcasting and discovery features needed - clients will always explicitly specify UNC address to access the resource.

share|improve this question
up vote 2 down vote accepted

Your memory of ports 137 and 139 relate to NetBIOS over TCP/IP. SMB directly over TCP uses port 445.

Allowing TCP port 445 from a Windows XP client to a Samba or Windows Server computer will permit the client to "map" a "drive" to SMB shares exported by the server computer so long as you use the IP address of the server computer in such a request. Just to be sure, I verified with Windows XP Professional 32-bit SP3 against Windows Server 2003 R2 SP2 and Samba 3.0.33 running on CentOS 5.5, through a packet filter that allowed only TCP port 445 traffic from the client to the server. I was able to "map" "drives" and access files on the remote machines.

share|improve this answer
It'll work like a charm. Only thing to be aware of is, if this is traversing the public Internet, there's a fair chance tcp/445 might be blocked by one of your ISPs on either end. – BMDan Jul 19 '10 at 1:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.