Cannot connect, ping, resolve DC server.

[Sir Asvald]

This is starting to piss me off so much, this is my 3rd post. I've had this issue for more than 1 week. My setup as it is:

 

1 DC, Windows Server 2012 R2 datacenter

2 Exchange 2010's. On-premise and a VPS. 

 

The IP of the DC server is 192.168.1.252 

Exchange on-premise is 192.168.1.82

VPS is connected via VPN, IP is 192.168.202

My PC IP is 192.168.1.120

My Laptop IP is 192.168.1.35 

Issues I'm facing. I cannot ping the DC using the FQDN or by it's name, from my PC nor from the On-premise Exchange server. The DC is called HQ-DC1, The on-premise server is called hq-leo.

I can't ping the domain, which is learntotechsolutions.com. I can ping hostnames from the server itself and it resolves to itself and from the VPS Server. I have no idea what the issue is, before anyone asks, yes, I've added the IP of DC in the DNS server settings on all PCs and my laptop. 

 

Someone please help me. 

 

[zombienerd]

Double check you have set the subnet mask the same for all the machines.  I've run into similar issues when I fat fingered a manual IP config to 255.255.0.0 instead of 255.255.255.0

[Sir Asvald]

11 minutes ago, zombienerd said:

Double check you have set the subnet mask the same for all the machines.  I've run into similar issues when I fat fingered a manual IP config to 255.255.0.0 instead of 255.255.255.0

Everything is in check. Now I can't even connect to my VPN anymore. This is seriously taking the piss. Running my business here and I cannot connect to my email server nor my website. All bloody broken

[zombienerd]

The next step I would take is to rule out hardware issues.  Try booting your DC from a Linux USB, assign your static IP, then see if you can ping it from the other machines.  This would remove all Windows-related software issues.  If you can ping the server, then you know there is a config issue, and I'd wipe the box, restore from backup (or if the server is new, just re-install from bare metal).  If you cannot ping, then your NIC, router, or cabling could be at fault.

[NelizMastr]

You have to manually point all clients DNS setting to the domain controller if you’re not using the DHCP role. 

[Sir Asvald]

54 minutes ago, NelizMastr said:

You have to manually point all clients DNS setting to the domain controller if you’re not using the DHCP role. 

DHCP comes from my ISP Router. Router has the settings for network

[bcguru9384]

4 hours ago, Abdul201588 said:

DHCP comes from my ISP Router. Router has the settings for network

try running netsh dnsclient then run /? for help list

somewhere in here you can tell dns 192 gateway to be mode=both

primary is default = wan dns resolves 

both=wan&&lan dns resolveable

dhcp service on router should have a basic table data for dns resolutions(devicename, mac, ip address)

[Jarsky]

So when you check your clients ipconfig - theyre definately showing your DNS Server IP as 192.168.1.252 ?

Sometimes doing a setup this way depending on the router, your client can get your ISP's DNS servers as advertised by your router.

[Sir Asvald]

On 12/24/2017 at 5:58 AM, Jarsky said:

So when you check your clients ipconfig - theyre definately showing your DNS Server IP as 192.168.1.252 ?

Sometimes doing a setup this way depending on the router, your client can get your ISP's DNS servers as advertised by your router.

Sorry, Should've replied sooner. I ended up reinstalling the DC. It's working fine.