Windows 10: How can I use an AAAA-only domain for SMB connection

My ISP blocked 445 port for SMB. Therefore, I setup SMB over QUIC with my own domain. However, I only have IPv6 IP in WAN. I tried to connect to my SMB server over QUIC/443 port but failed.net use * \\quic.mydomain.com\Share /TRANSPORT:QUICSystem error 67 has occured. The network name cannot be found.I can connect to my SMB by any following waysnet use * \\quic.mydomain.com\Share /TRANSPORT:QUIC In LAN, I set an A record in the nameserver pointing to my LAN IPnet use * \\xxxxxxxx..ipv6-literal.net\Share In LAN, this goes to TCP/445 portHow can I use SMB in this 443 blocked, IPv6 IP only ne

:)

 

How to solve problems with accessing, discovering and connecting to NAS with SMB connection from Windows 10

I am experiencing difficulties with accessing, discovering and connecting to my NAS with SMB connection from Windows 10.

I have tried most of the solutions suggest on the Web, but avail, none of them worked.

• Enabling SMB v2 and restarting
• Checking SMB v1 in Windows components is ticked on
• Etc.

It seems that Microsoft has broken something though their patches

If anyone can supply me with a permanent/ final fix,
not workaround, please post it here.

 

How to solve problems with accessing, discovering and connecting to NAS with SMB connection from Windows 10

I am experiencing difficulties with accessing, discovering and connecting to my NAS with SMB connection from Windows 10.

I have tried most of the solutions suggest on the Web, but avail, none of them worked.

• Enabling SMB v2 and restarting
• Checking SMB v1 in Windows components is ticked on
• Etc.

It seems that Microsoft has broken something though their patches

If anyone can supply me with a permanent/ final fix,
not workaround, please post it here.

 

UnattendedJoin error: failed to find the domain data (0x6e)

Thanks for the suggestion! I don't want to add a domain account, as this is a generic unattended install that will be used for all company machines. Do you think it's possible that the computer would join the domain if, instead of using UnattendedJoin in specialize, I used your steps but left out the specific account? The other thing I was thinking was to use a generic account to allow the domain join during the specialize step. I added a machine password in the UnattendedJoin component, and instead of getting the error listed above, I got an authentication error, which makes me think I could probably do a secure join instead of the unsecure join. Thoughts?