Windows 10: Server network cannot access with name but accessible with ip

I have a Server and a few windows 10 computers in my office. Usually i can access the server network from all computers by typing \\"servername". I restarted the server today morning and after that two of my windows 10 computers dont connect to server when I type \\"servername", but if i type the ip address \\192.168.0.11, it is connecting. My other six computers doesnt have any problem with responding to server name.

Can some one help me fix these two computers? I am not a professional IT person, it would be a great help if someone can give some step by step process.

My server is Windows Server 2012 R2

Computers i want to connect are Windows 10 Pro


Thank You

:)

 

Cannot access server 2003

The problem I am having is that no computer can access the server (with MS windows server 2003 installed) yet it can access all other computers.

By not being able to access it I mean that it cannot be pinged in command prompt. The funny part is, the server DOES come up in "Network" but when I go to double click it it comes up with the usual: "Windows cannot access *name*. Check the spelling of the name. Otherwise, there may be a problem with your network. To try and resolve....press Diagnose"

I have tried to connect via IP address with no results.

The server is running NO firewalls (not even Windows firewall, as it wouldnt even start). It can connect to the network (other computers) or internet with no problems at all.

Also, I have removed DNS/DHCP. The only two "servers" I have running are remote access and Print server.

 

WinServ2003 Internet Access

Well, how I think it is working is my cable modem is assigning IP and DNS information to my router. My router is then acting as a DHCP server and assigning everything to computers on my network. The computer I'm trying to set up as a server isn't configured as a DHCP server, all I'm really wanting to have it do at the moment is be a file server and maybe do some folding.

I haven't tried, but right now I don't think It is even connecting to my network. It is assigning itself some funky IP that is not the standard 192.168.1.x that everything else on my network gets. I can't even access my router using the computer at the moment, but I can access it using my main rig.

I haven't tried to implement your suggestions yet though. So I'll have to wait and see what happens.

 

How to get multiple accesses to a NAS server?


I have need to get access to 2 shares on a NAS server using different credentials - one set of credentials for occasional access to a secured share; another for continuous access to a public share. I just found out that Windows does not allow this without some game-playing.



I've seen 2 circumventions. For one of the connections:

1. use the server's IP address, or
2. create another DSN name for the server and refer to that other name.

#1 is not a good solution unless I give a static IP addr to the server. I could do that, but I'd rather not.

I don't know how to do #2. Somehow put a CNAME record in my routers DNS server? Get the server to supply multiple DNS names? Dynamically add a record to Windows' etc\hosts file by a script?

Does anyone have experience with this?