SMB fileshare - looks like it is timing out on the MS side

Scott Fergusson 1 Reputation point
2020-10-08T16:02:53.34+00:00

I'm trying to mount a fileshare with my mac, and am getting a timeout. Here's the traceroute:

sudo traceroute -p 445 XXXX.file.core.windows.net

traceroute to file.blz21prdstr06a.store.core.windows.net (20.150.90.40), 64 hops max, 52 byte packets
1 rt-ac88u-1530 (192.168.1.1) 0.929 ms 0.509 ms 0.351 ms
2 gateway.home (192.168.254.254) 1.118 ms 1.097 ms 0.907 ms
3 fdr02.ftwy.in.frontiernet.net (74.42.148.177) 6.004 ms 4.665 ms 5.302 ms
4 ae16----0.car01.ftwy.in.frontiernet.net (74.42.113.133) 5.906 ms 5.581 ms 6.118 ms
5 * * *
6 ae14---0.cor01.chcg.il.frontiernet.net (74.40.5.105) 9.953 ms 10.147 ms 9.103 ms
7 ae0---0.cbr01.chcg.il.frontiernet.net (74.40.4.138) 9.069 ms 9.736 ms 10.319 ms
8 frontier.chg-96e-1.ntwk.msn.net (207.46.219.152) 9.998 ms 10.320 ms 9.781 ms
9 ae30-0.icr01.ch2.ntwk.msn.net (104.44.237.17) 11.259 ms 10.709 ms
ae35-0.icr01.ch4.ntwk.msn.net (104.44.237.19) 11.031 ms
10 be-120-0.ibr02.ch2.ntwk.msn.net (104.44.11.13) 26.690 ms
be-100-0.ibr01.ch4.ntwk.msn.net (104.44.11.7) 29.106 ms
be-100-0.ibr01.ch2.ntwk.msn.net (104.44.11.252) 25.484 ms
11 be-3-0.ibr01.cle30.ntwk.msn.net (104.44.7.113) 28.270 ms
be-10-0.ibr04.bl20.ntwk.msn.net (104.44.28.233) 27.901 ms
be-5-0.ibr03.bl20.ntwk.msn.net (104.44.28.219) 30.589 ms
12 be-8-0.ibr04.bl7.ntwk.msn.net (104.44.28.120) 28.094 ms
ae162-0.icr02.bl20.ntwk.msn.net (104.44.21.234) 26.754 ms
ae142-0.icr02.bl20.ntwk.msn.net (104.44.21.224) 25.645 ms
13 * ae140-0.icr01.bl7.ntwk.msn.net (104.44.21.206) 28.191 ms *
14 * * *
15 * * *
16 * * *

Looks like it is hanging up at MS?

Thanks,

Scott

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,213 questions
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,874 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. deherman-MSFT 35,011 Reputation points Microsoft Employee
    2020-10-08T18:09:15.837+00:00

    @Scott Fergusson To test port 445 TCP with traceroute please make sure to add the -T flag. Also make sure that if you have a firewall enabled it is allowing the client IP. See Cause 2: Virtual network or firewall rules are enabled on the storage account. Port 445 is not blocked on the Azure side and should be open. However if it is blocked from the ISP you may need to use one of the available workarounds such as deploying File Sync, VPN, or the REST API.

    Hope this helps. If you have additional questions or issues please let me know.

    ---------

    Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.