Adding client to server

[Eirikstrand1996]

hi, so i have a local windows 2016 server with DNS DHCP and AD, 
im connected to a router with 192.168.1.1
and did  disable DHCP on the router.

so i think i configured every thing right and the client had preffered DNS to the dns server.
but the only way i could get connection is with using default gateway to 10.0.2.1 .
make no sense 

Edit: now i can what ever on the default gateway and it works, as long that is static, like 
192.168.1.20
255.255.255.0
1.0.0.0
 

[NelizMastr]

???????

 

There's a ton of missing information here.

 

What network range is your DHCP server leasing?

Which gateway did you configure in the DHCP server options?

Can your client ping that gateway?

[myselfolli]

Yeah, there's nowhere near enough information here to help you with your problem...

[Eirikstrand1996]

6 minutes ago, NelizMastr said:

???????

 

There's a ton of missing information here.

 

What network range is your DHCP server leasing?

Which gateway did you configure in the DHCP server options?

Can your client ping that gateway?

scope is 192.168.1.30-200
the gateway is 192.168.1.1
no i can not ping since it is local

[NelizMastr]

27 minutes ago, Eirikstrand1996 said:

no i can not ping since it is local

I don't think you know what a ping is then. It's a crucial tool for testing reachability on a network, not just to the internet. If your client can't reach the server or the gateway, then your issue is with the client.

[Mikensan]

4 hours ago, Eirikstrand1996 said:

hi, so i have a local windows 2016 server with DNS DHCP and AD, 
im connected to a router with 192.168.1.1
and did  disable DHCP on the router.

so i think i configured every thing right and the client had preffered DNS to the dns server.
but the only way i could get connection is with using default gateway to 10.0.2.1 .
make no sense 

Edit: now i can what ever on the default gateway and it works, as long that is static, like 
192.168.1.20
255.255.255.0
1.0.0.0
 

You said your gateway is 192.168.1.1 - so what is "10.0.2.1"? The Windows 2016 Server is not a gateway, it is a DHCP and DNS server. So nothing should be using its IP as a gateway. You also aren't saying if the issue is with the server or the client - hard to help you.

 

If your issue is DNS:

On your Windows 2016 Server, you need to configure NIC's DNS as 127.0.0.1, and in the DNS role you need to add a forwarder (192.168.0.1) so it can resolve internet DNS records. Then you need to edit the DHCP scope to set the DNS server as 192.168.1.?? to whatever your Windows 2016 Server's IP is.

 

On the client, you need to confirm you can resolve DNS from the Windows 2016 Server. In Command prompt do NSLOOKUP SERVERHOSTNAME, if that works then proceed to external NSLOOKUP WWW.GOOGLE.COM.

[Mikensan]

Also it would be extremely helpful to label every IP, so far you've given us 4 IP addresses:

 

192.168.1.1 - is this a ASUS Wifi router, Cisco ASA, pfSense?

192.168.1.20 - Is this the Windows Server 2016 or your client?

10.0.2.1 - What is this?

1.0.0.0 - this isn't an IP

[JaimeAOC]

Make sure the DHCP scope is authorized and running.

In the client leave the IP on automatic but change the DNS ip to the IP of your server (not the router)

 

Check if you can ping the server's ip.