Allowing changing of port 445 so I can access Azure File Storage using Comcast
When I try to map to a network share in Azure File Storage I get an "Error 53" message. I'm using Comcast and it seems port 445 is being blocked by them. I'd like to roll this feature out to mobile users (many use Comcast or residential internet) and we can't realistically ask them to call their ISP and make a change. I could use a VPN I suppose but this would defeat the purpose of easily hosting the files in Azure.
Gene G commented
Yes, why can't we just set an alternate port of our choice (NAT?) on Azure Storage? The VPN option is not good.
Dan Sarandrea commented
Just found this suggestion thread. Wow, I guess I am not alone thinking that MS is dropping the ball on this. I have several clients whose operations could be "cloudified" if Azure File Storage could be made to work for them. Unfortunately, their ISPs block port 445 as well. Yes there are workarounds, but small business Clients are not interested in spending thousands of dollars for overpriced VPN equipment that slows down connectivity, or paying other thousands of dollars to their ISPs for a special connection to use Azure when they should be able to use AFS without jumping thru $$$ hoops. Apparently all that needs to happen is for some Boss at Azure to decide to have the AFS thing work on a port other than 445.
Dan Sarandrea commented
What is the point of Azure File Storage and developing SMB v3.x when a huge percentage of ISPs block the port that your services use?
C'mon Azure People, get with it! Make it so that Azure File Storage can use some other port besides the beyond-hope 445!!! SMH!
Junwei Huang (MVP) commented
The ability to change 445 port is the best way to resolve the Azure File connection problem. Please update!
Azure User commented
Why is Microsoft not working with ISP's to get past outdated security concerns that impact access to Azure services?
Chris Little commented
with ISP blocking these ports this would be wonderful to have a workaround without the need for azure file sync
Chris Little | Architect
Microsoft Certified Solutions Expert: Cloud Platform
Comcast Business and Xfinity Home both block all traffic on port 445. Plenty of other ISPs do as well, Microsoft even maintains a list of which ISPs block which ports. MS needs to add the ability for Azure and Windows to use alternate port numbers.
Azure and Comcast don't care - the file share thing is a waste of time given MOST ISPs block port 445 - Microsoft obviously knows...