Mapping network share drives on a Domain


first tried upgrading system prepared windows 7 , transferred setting replace existing machine test windows 10.  once upgraded windows 10, 1 of mapped drives on domain can not connect.  have mapped drive 2003 server, a windows 7 pc, , 2012 server share that work fine.  drive can not connect on server 2008 r2 file server.  share on 2008 server can accessed xp, window 7, , windows 8.1. thought may have gone wrong in upgrade process did clean install of windows 10, , results same.  missing something?

hi poshkid,

thanks sending me other set of traces, in analyzing connection attempts have been able narrow down issue. reason encountering issue server2003 fileshare server not listening on tcp port 445 either directly being blocked firewall or network device blocking traffic.

in reviewing reason why windows 10 attempting use tcp 445, noticed when establishes connection on tcp port 139 sends negotiate response indicating versions of smb supports. when server responds back, indicates use smb2 in windows 10 gracefully tears down session , attempts establish connection on tcp port 445 never receives response.

in examining fileshare server trace, other connections being made other clients not advertising can connect on smb2 or smb3 clients , server continue use smb on netbios (tcp port 139) complete connection.

at point, can disable smb2 or smb3 directly using information documented in http://support.microsoft.com/kb/2696547, not recommended , better approach open tcp port 445 allow faster network transfers of data , less network congestion. please feel free reach out me questions may have.

regards,


adam rudell | sr support engineer | windows beta | microsoft corporation



Windows 10 Insider Preview  >  Windows 10 Insider Preview Setup and Installation



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group