Over the last week I've migrated all of our services running on Server 2003 to our 2012R2 environment successfully.
This included: AD, DHCP, DNS, Print server, File serving using the migration tool, and in the environment all PC's work well, except for 2 Win10 PC's that were upgraded to Win10 prior to me starting here.
All other PC's are W7Pro with one XP Pro PC. All able to see file server shares and print server shares on the new server.
Old server name: CHMCMD1 New server name: CHMCDC01
As part of the file server migration, I also renamed the old server to CHMCMD1OLD and registered its previous computer name CHMCMD1 on the new DC01 server using the NETDOM COMPUTERNAME CHMCDC01 /ADD
This all went well, and everything on the network is working except these two Win10 PC's with their network issue.
They can ping CHMCDC01 and it resolves to the IP 192.168.1.21, and they can ping the added computer name CHMCMD1 and it also resolves to the IP 192.168.1.21 as I expect.
Just when trying to now map to the network share, I get a Network Error: Windows Cannot access \CHMCMD1\ Error Code: 0x80004005 Unspecified Error.
I've looked into this and there is plenty of talk about possibly being a WINSOCK error on the WIN10 terminals, but I currently doubt that as the fixes I tried around that haven't fixed the problem.
Can anyone suggest any ideas on what I can try to resolve this? Only happening for 2 clients out of 80. These two are the only two that are Win10, and they were able to map to the server share fine with server03.
User contributions licensed under CC BY-SA 3.0