Application server running Windows 2012 r2 Standard does not appear to be on the network. Cannot resolve by name from client but can resolve by ip address.

Windows Server 2012 r2 Standard Application Server appears to be a stand alone server but is on a network.  The server is joined to the domain (I checked that), but my clients cannot connect to host by name - if I type in the IP Address the clients find the server.   Everything appears to be turned on as far as network discovery, services, etc.  When I go into Manage and try to add users or anything - my only location is the server's local name (i.e. server1) - If I select Locations - there is nothing else there.  I should be able to select my domain, but it does not appear.  Any suggestions?  Attached is a screen shot.
Screen-Shot-2018-02-07-at-10.28.22-A.png
manch03Asked:
Who is Participating?
 
manch03Author Commented:
I apologize for not getting back sooner.  I had a family emergency so I am back at it.  I ended up making this server a domain controller and it is now functioning on the network.  I have no idea why it was not recognized on the network prior to promoting to a DC.  It is functioning properly now.
0
 
Radhakrishnan RSenior Technical LeadCommented:
Hi,

In the server's n/w card properties, what's the DNS address set?. Also, what's the output you get when you perform 'nslookup' (start>>run>>cmd>>nslookup).

Since it's a domain joined server, go to your internal DNS server and make sure this server has got a 'Host A record' which pointing to it's correct IP address?

Also, what's the user type which you logged onto the server? did you tried to login as local administrator (or domain admin) and checked?
0
 
manch03Author Commented:
I have not assigned a static IP - does that make a difference?  On my old server - I had the same issue except it had a static ip.
This is a working server, so I can't really assign an ip right now.  I checked the DNS server and it has an iPv6 address.   I think you are onto something here because yesterday I disabled the ipv6 on the network card.  I will turn that back on and perhaps the clients will be able to resolve to host.  I log into the domain - it is not a local account.  But I will definitely go in and add the ipv6 back.  I will assign an ip tonight.
0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

 
Radhakrishnan RSenior Technical LeadCommented:
Okay, let me know how it goes!
0
 
manch03Author Commented:
I assigned the ip but I think I have to reboot?  Or maybe it needs to replicate, but I will let you know.
0
 
manch03Author Commented:
I have waited several hours - I didn't do a reboot, but I still cannot see the network from that server.  I checked the DNS - it is not routing back to the IP address but to the ipv6 string.  I also looked at my main domain controller - it has two records in DNS - both the ipv6string and the ip address.  This may be the issue?  

However, I have my old server which has the correct ip address listed but I also had that issue on this server.  I made it work, but I would like to get this fixed.  Obviously something is not talking correctly.  I wanted to update this thread.  As soon as the users leave, I will reboot that server, and disable the IPV6 network connection on both of the servers.  Do you think that has anything to do with it?
0
 
manch03Author Commented:
I rebooted that server and nothing changed.  It is almost as if the server thinks it is a stand alone server not on a network, but shows up under the DNS with a host record with the correct ip address.   I still cannot change the Location to the network when I look at users - I only see the name of this server.
0
 
manch03Author Commented:
I just noticed when I was logging in - "please wait for the local session manager"  I am logging in with my domain credentials and it has the domain name...  hmmm
0
 
Radhakrishnan RSenior Technical LeadCommented:
Hi,

Worth to disjoin from domain and re-join if already not tried.
0
 
manch03Author Commented:
I was thinking that too - I am not on site and I do not want to unjoin and then not be able to reconnect.  I will try that too.  It's almost as if it thinks it is a server with no domain on it's own, even though I am being authenticated by the domain controller (I have no local log in for myself).  Something is not communicating.
0
 
manch03Author Commented:
Ok, I went ahead and unjoined and rejoined (nobody is in today)  Made no differnence.
0
 
manch03Author Commented:
How do I get the domain controller to recognize this application server as a member server?  Even after assigning a static ip address and rebooting, the server still shows up as  a workstation and not a server in AD.  I do not have a whole lot of experience with windows server 2012, but is that normal?
0
 
Radhakrishnan RSenior Technical LeadCommented:
Hi,

Open Active Directory Users and Computers from the DC, and see if the member server listed?

Is this just 2012 server or 2012R2? If it's not R2 then I suggest you to install the same.
In the initial post, I asked about nslookup, can you post the result here?
Is the server running with up to date windows update?
Are you able to access shares from itself n other dc's share?
What's the status of windows firewall? If profiles of windows firewall is on, can you make it off, reboot n check.
0
 
manch03Author Commented:
I just looked in the server manager - it is not installed as an application server but a file and storage and print and document server (roles).
It is 2012R2.

I typed nslookup and it routes back to the domain controller.

I can access shares from the other dc's and shares.

There are 3 options for the firewall - I turned off the domain firewall (it was on).
0
 
manch03Author Commented:
The server is listed on the domain controller, but under workstations.  I do not see a Server folder (like the older version of windows server) on the domain controller.  I didn't answer that question from your post.
0
 
Radhakrishnan RSenior Technical LeadCommented:
Hi,

As long as the server is listed in AD then that's fine, no matter which location it's belongs to apart from any specific GPO linked into that OU.

Another thing to try is adding a 'host' entry in the 'host' file (C:\Windows\System32\drivers\etc\hosts). Open the file in notepad, type the hostname and IP address of the server in it, save the file and check the issue (if issue didn't resolve, revert the changes).
0
 
Seth SimmonsSr. Systems AdministratorCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: manch03 (https:#a42507074)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.