Cannot connect to Windows 2012 R2 via netbios name
At some point today our Windows 2012 R2 became unconnectable via its usual netbios name - it can be accessed using \\192.168.10.52 but not by name.
I've restarted it, restarted router, pulled power to switches, but still the same problem.
I'm currently wondering around 20 desks trying to explain to people how to access the server.
Any help appreciated !!
I've restarted it, restarted router, pulled power to switches, but still the same problem.
I'm currently wondering around 20 desks trying to explain to people how to access the server.
Any help appreciated !!
did you check DNS?
Is netbios over tcp/ip enabled?
check dns server and or try to edit the host file on the workstation to see if it resolve via host name..
e.g.
192.168.10.52 windows2012servename
102.54.94.97 rhino.acme.com
e.g.
192.168.10.52 windows2012servename
102.54.94.97 rhino.acme.com
ASKER
No to DNS - i have a draytek router issuing DHCP, the server is the only PC we can no longer connect to by name, all other PC's can still see/connect to others.
I enabled netbios over tcp, rebooted by didnt change anything
I enabled netbios over tcp, rebooted by didnt change anything
I hope you are using static ip on the server. try to run ipfonfig /flushdns on the workstation via command line..
ASKER
No server has had dynamic address forever - never gave it a static.
flushdns did not make a difference on a workstation.
However i've just been informed that some people could still connect via the name, while most couldnt..
Also, one of the workstations can still connect using \\leviathan2 even though i renamed the server to \\leviathan1 and rebooted it.
I have no DNS server here
flushdns did not make a difference on a workstation.
However i've just been informed that some people could still connect via the name, while most couldnt..
Also, one of the workstations can still connect using \\leviathan2 even though i renamed the server to \\leviathan1 and rebooted it.
I have no DNS server here
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Shaun is correct.. use static IP...
No, Dubs, you are right. I saw the requirement for static IP but I assumed it was static because of the IP in OP's post.
ASKER
Ok - let me set a static and see what happens - thanks
ASKER
Ok - Static fixed it - Thank you !!
Before i close the question - any suggestions on why it has worked on DHCP for the last 4 years, and all of a sudden stopped today ?
Before i close the question - any suggestions on why it has worked on DHCP for the last 4 years, and all of a sudden stopped today ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Murphy... :P
ASKER
Well things seem have deteriorated....
Since changing to Static, i now have the following situation.
My workstation can access \\leviathan2 fine - i can see all folder files etc.
All other workstations bar one cannot see it unless they use \\192.168.10.221 (most restarted last night following update)
Now this is where it gets bizzare, one workstation can see \\leviathan2 but only limited folders, and a few files, other folders are showing but with an x and when clicked on telling him not authorised.
However if he uses \\192.168.10.221 he can access everything perfectly.
All machines are running Windows10.
Further thoughts appreciated
Since changing to Static, i now have the following situation.
My workstation can access \\leviathan2 fine - i can see all folder files etc.
All other workstations bar one cannot see it unless they use \\192.168.10.221 (most restarted last night following update)
Now this is where it gets bizzare, one workstation can see \\leviathan2 but only limited folders, and a few files, other folders are showing but with an x and when clicked on telling him not authorised.
However if he uses \\192.168.10.221 he can access everything perfectly.
All machines are running Windows10.
Further thoughts appreciated
ASKER
Sorted :)
When i applied the static IP, it created a Public Network rather than Private - changed, and now all workstations can see server
Thanks all for help !!
When i applied the static IP, it created a Public Network rather than Private - changed, and now all workstations can see server
Thanks all for help !!
ASKER
Thanks everyone !!