How to access SMB share from windows on a different port number IE \\127.0.0.1:4445\

mike johnson 11

I can do this on mac, bsd and linux but not windows. Its even worse I cannot even bind port 445 on 127.0.0.X or create another adapter and bind that port, windows automatically captures it.

I'd like to do secure tunnels to other machines, VM's and docker containers on the local network and/or machine, but since I cannot bind 445 since it is already bind by windows and I cannot have explorer use a different port like \127.0.0.1:4445\ like all other OS's allow we are stuck with no windows support.

Is there a solution?

Hung-Chun Yu 976 Reputation points Microsoft Employee

2022-06-30T16:16:02.127+00:00

Hi @mike johnson

After reviewing your questions, it is not related to Protocols issues outlined here http://aka.ms/openspecs. I am removing [openspecs-windows-filesharing] tag from the post, instead I am adding [windows-server] tag,

Thank for contacting Microsoft Open Specifications Support.

Hung-Chun Yu
Microsoft Open Specifications Support
mike johnson 11 Reputation points

2022-11-01T15:24:44.233+00:00

I have solved this problem by finally finding a replacement for windows file explorer that supports this basic functionality that exists on all other platforms.

It is available on the microsoft store and is called "Owlfiles". It is a very nice app with all the functionality of Windows File explorer plus much more. It allows you use port numbers on
your shares like \127.0.0.1:4445. We were limited to using MAC and Linux for our docker shares, but now we can use windows also.

Owlfiles can be found on the Microsoft Store:
https://www.microsoft.com/store/productId/9MSQ3SZK42KP

Share via

How to access SMB share from windows on a different port number IE \\127.0.0.1:4445\