New Windows 10 PC will not connect to server 2012 r with server name

Question

New Windows 10 PC will not connect to server 2012 r with server name

Scott Purtan 6

I have a new windows 10 pc and I am trying to connect to the server with it. I can get to the server by IP address but not with the server name, in this case it is \Server-01. It is telling me that the dns server is not responding or incorrect. I have several other PCs connected and working on this network to the server. All of the services are running and I can ping \Server-01 at command prompt. I have flushed dns etc. The other day I had this working and now it does not. There was a third party on this trying to install software from the server and then I now have this issue. I am not sure what they did and do not know what they might have changed. The install of the software was unsuccessful and called it a network issue. To go further they could not install the software off the server with the server name so they started using the IP address to the server to see if that resolved the install. That is when I believe it stopped communicating with the server name. Any help would be appreciated. Thank you..

3 answers

Your answer

Answer 1

MotoX80 36,416

You will need to describe your network environment.

For example, here at my home I have a WIFI router that connects to the internet. All of my PC's and test VM's use DHCP. When the PC boots, DHCP acquires an IP address from the router. The NIC's are set to "Register this connections address in DNS". When I run NSLOOKUP against a name or IP address, it displays the PC's IP or it's name. All of my PC's use the WIFI router as the DNS server. (The default from DHCP.)

There was a third party on this trying to install software from the server and then I now have this issue. I am not sure what they did and do not know what they might have changed.

Your server/desktop/network admin should have been looking over their shoulder to watch what they were doing and verify that the decisions that they made were consistent with your organizations polices and help them work through any issue that they might encounter.

Is this a home network? Small business network? Do you use Active Directory? Who provides desktop and server support? Have they investigated this problem? What DNS servers do your machines use?

Scott Purtan 6 Reputation points

2021-03-31T21:11:16.627+00:00

This is an office network. There are a total of 7 PCs and One server. All connections are wired. The address comes from DHCP from the Internet company modem. All PCs can access the server except the new PC. the IP address is in the same schema of the network. I can ping the IP address of the server but cannot ping \Server-01. The PC shows up in the network on the server and the server shows up on the new PC. When try to go to \Server-01 or select it from Win 10 Network it comes up that it cannot connect. When I run troubleshooter it tells me that the DNS isn't responding. I have checked over all services that should be running, I have went into Credentials of Win-10 and dropped the IP address to the server as well as the old connection to \Server-01. The network is using a workgroup name it is not on a domain.
Scott Purtan 6 Reputation points

2021-03-31T21:28:54.613+00:00

Small dental office network. The only reason the server is in place is for the Software they were trying to install. They know there system and how it works. I am not the Admin, they do not have an admin. They hired someone to come in and setup the server and network. In my opinion they set this up like a home network, probably because that is all they knew. They did not change anything on the PC directly. They have troubleshooting software they were using. I did notice that they went into the registry but they did not change anything, I think they were looking to see if something was correct.

Answer 2

Sounds similar to my home network. Open a command and run "ipconfig /all". Here's what I get.

Wireless LAN adapter Wi-Fi:  
  
   Connection-specific DNS Suffix  . : home  
   Description . . . . . . . . . . . : Dell Wireless 1707 802.11b/g/n (2.4GHZ)  
   Physical Address. . . . . . . . . : 74-29-AF-48-F6-11  
   DHCP Enabled. . . . . . . . . . . : Yes  
   Autoconfiguration Enabled . . . . : Yes  
   IPv6 Address. . . . . . . . . . . : fd00::49de:8633:d70:20d(Preferred)  
   Temporary IPv6 Address. . . . . . : fd00::30e8:82f0:1cda:bc9c(Preferred)  
   Link-local IPv6 Address . . . . . : fe80::49de:8633:d70:20d%8(Preferred)  
   IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)  
   Subnet Mask . . . . . . . . . . . : 255.255.255.0  
   Lease Obtained. . . . . . . . . . : Wednesday, March 31, 2021 4:55:44 PM  
   Lease Expires . . . . . . . . . . : Thursday, April 1, 2021 4:55:43 PM  
   Default Gateway . . . . . . . . . : 192.168.1.1  
   DHCP Server . . . . . . . . . . . : 192.168.1.1  
   DHCPv6 IAID . . . . . . . . . . . : 74721711  
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-F3-F7-E4-74-29-AF-48-F6-11  
   DNS Servers . . . . . . . . . . . : 192.168.1.1  
   NetBIOS over Tcpip. . . . . . . . : Disabled

Are the addresses for DHCP Server and DNS Server in your results the same IP address? My PC has an IP address of 192.168.1.3. From the command prompt run an NSLOOKUP on some of the IP addresses on names of your PC's, Do any resolve?

This is very similar to this post that I helped another user with. In his case his router's DNS did not register his local PC names. We verified that all of the Network Discovery services were running as DSPatrick has pointed out. You might want to look through that post because the troubleshooting steps are the same.

https://learn.microsoft.com/en-us/answers/questions/302088/how-to-switch-from-a-call-by-ip-address-to-a-call.html

Scott Purtan 6 Reputation points

2021-03-31T22:03:52.787+00:00

This network has a 192.168.0.1 as default. DNS is 209.18.47.63 and 209.18.47.62 both ping successfully. I will look at the other post. Im going to check first i flushed, renew, release, etc on the dns and rebooted
Scott Purtan 6 Reputation points

2021-03-31T22:16:02.263+00:00

When I do a nslookup it comes back with dns-cac-lb-03.rr.com cant find 192.168.0.23 non existant domain. Which is the IP address that it has issued to the machine.
Scott Purtan 6 Reputation points

2021-03-31T22:39:43.653+00:00

In fact when i do the nslookup on the server address it comes back the same.. How can that be when i have other PCs communicating with it??

Answer 3

MotoX80 36,416

You have a problem similar to the other user. You can't register 192.168.0.23 because every other Charter Communications (TWC) customer could have that address in use.

In my opinion, your router is not configured properly, but that may be a "that's how this model works" situation. My router provides DNS so that my local machines can get their name registered and resolved. If I browse Yahoo.com, then my router will query external (internet) DNS servers to get the IP address.

Your PC's are going straight to the internet DNS server and can't resolve the local names.

Try running the Powershell script in that other post and see if that fixes Windows Network Discovery.

Scott Purtan 6 Reputation points

2021-04-01T00:26:03.697+00:00

Yes i tried the script already earlier. It didn't help. Unfortunately i will not have the UBEE password until tomorrow to see what's going on in it. Once i get into it I will be able to see if that is an option or not. I really do not like the setup they have, but with a running office and going in and changing a bunch of stuff, could be disastrous. Especially with the software they are using.. I will post if I find anything..
MotoX80 36,416 Reputation points

2021-04-01T13:33:20.05+00:00

Yeah, rule number 1 is: don't break a production environment.

Check the Network on a few machines. Hit F5 for refresh. See what shows up.
Scott Purtan 6 Reputation points

2021-04-01T15:04:46.497+00:00

I actually did that a few days ago. All the other pcs are fine all PCs show up on all of them. Even the Server shows all including the new PC. I going in the office in a few. The issue they were having with the software was not a network problem. Its a windows problem. Error 1935 when they try to install. I have exhausted all the options for this, i believe, other than installing some fix program on the PC. I cannot understand how a new PC has this many issues.. There was a list i went through, about 10 or more things and really all the sites have the same procedures. Hopefully i can find something different to try to resolve that issue...
Scott Purtan 6 Reputation points

2021-04-01T16:06:04.76+00:00

I went into the office and got into the cable UBEE Modem. All the PCs are in the modem as their respective names. I am kind of lost on this. Especially when this was working before the other company remotely went in to try to install software.
MotoX80 36,416 Reputation points

2021-04-01T17:16:26.897+00:00

All the PCs are in the modem as their respective names.

But in order for other PC's to resolve the names, DHCP would need to configure each PC to use 192.168.0.1 (the router) as the DNS server. Using 209.18.47.63 as the DNS server will never find any machine on the local network. A DNS query will go straight to the internet.

Error 1935 is a new one for me. The first search result mentions an error in the file system transaction log. You might want to start a different thread if you need help with that.

I built a little .bat file that I called IsWindowsHealthy.bat that you can run to perform some basic tests. You could try that. It's here.

https://learn.microsoft.com/en-us/answers/questions/187906/can39t-solve-windows-update-error-0x80070002.html
Scott Purtan 6 Reputation points

2021-04-01T17:23:12.84+00:00

Thanks and i did start a new thread. I already did the transaction log thing twice... So I need to go to all the PCs and set the dns to 192.168.0.1?? It is strange to me because this has been setup and running the way it has with no issues. The only issue is the new PC..
Scott Purtan 6 Reputation points

2021-04-01T17:29:15.523+00:00

I ran your bat file. No errors. it did do a component store cleanup...
MotoX80 36,416 Reputation points

2021-04-01T17:48:45.743+00:00

No, you don't want to do that. We don't know how the router works. Ideally you would change the DHCP config in the router to tell clients to use 192.168.0.1. But you would also need to make sure that it's configured with the correct addresses for the internet DNS servers. I would assume that would be 209.18.47.63, but I would suggest a call to your ISP support folks to verify how to set that up. You don't want to make this situation worse and cripple all pc's in the office.

In any event, if network discovery is working for all machines except that one, then you may not have to change DNS servers. But you'll have figure out what's wrong with that one.

Are the Win10 machines at roughly the same patch level? When in doubt, reboot the sick pc again.
Anonymous

2021-04-05T06:39:14.76+00:00

Just want to confirm the current situations.

Please feel free to let us know if you need further assistance.

Share via

New Windows 10 PC will not connect to server 2012 r with server name

3 answers

Your answer