Hello! Maybe somebody can help me to realize my problem.
I have installed SE Server on PC with Windows Server 2016.
PC attached to the router1 with default gateway 192.168.0.1, and DHCP obtained Ip adress 192.168.0.9.
In SE server I success create Local Bridge to my network card and I do not enable secure NAT.
I have installed SE Client on the remote PC from remote office. This PC attached to the router2 with default gateway 192.168.0.1, and DHCP obtained Ip adress 192.168.0.222.
Then I initiate connect on client PC, i see this alert:
It dissapear after 10-15 seconds and I have connected client wich is can be reached with netbios name of this PC. But, if I look to virtual VPN adapter In network adapters, I see permanent identifying process, wich never be stopped:
and if I look to status of thic connection, I see no default gateway ip, and some strange IP adress from different subnetwork:
If I setup virtual VPN adapter as static ip with this values:
ip: 192.168.0.70
subnet: 255.255.255.0
default gateway: 192.168.0.1
then connection executed quickly, and the client successfully appears on the local network on the server side, and it can be accessed both by netbios name and by ip address.
What I must to do, for my client can obtaine ip adress from 192.168.0.XXX subnet with DHCP-server on router1?
Many thanks for any help!
Obtaining IP
-
- Posts: 4
- Joined: Tue Nov 23, 2021 1:36 pm
Obtaining IP
Last edited by taravasya on Wed Nov 24, 2021 11:14 am, edited 1 time in total.
-
- Posts: 139
- Joined: Sat Feb 13, 2021 10:22 pm
Re: Obtaining IP
When you say: "DHCP obtained Ip adress 192.168.0.222."
That does not match what you write later: IP 169.x.y.z
Having an IP Adress in the 169.x.y.z range means normally the client was not able to get an IP Adress, so it assigns an IP Address itself.
Why do you know you got an IP Adresse to 192.168.0.222?
Check the DHCP server if it really assigned this address, and, if it matches the MAC Address of the VPN Client. Check if the DHCP server has still enough empty space in its address pool.
Maybe disable any firewall running on the VPN Server and on the client for testing.
That does not match what you write later: IP 169.x.y.z
Having an IP Adress in the 169.x.y.z range means normally the client was not able to get an IP Adress, so it assigns an IP Address itself.
Why do you know you got an IP Adresse to 192.168.0.222?
Check the DHCP server if it really assigned this address, and, if it matches the MAC Address of the VPN Client. Check if the DHCP server has still enough empty space in its address pool.
Maybe disable any firewall running on the VPN Server and on the client for testing.
-
- Posts: 4
- Joined: Tue Nov 23, 2021 1:36 pm
Re: Obtaining IP
Ah.. I see there IP is: 169.x.y.z
Its on the screen with properites of my VPNvirtual netwok card, after client connected to server. This ip is obtained... I don’t know exactly from where is obtained, and this is first part of my problem.
Its ip adress what obtained from router2 in local network of remote office. I know is because I see it in properies of my Local Network Card status.
Remote PC does NOT appear in DHCP server of my router1. And this is second part of my problem.
I`m sure address pool is have enough free ip adresses. Our networks not so big. Max 10-15 devices in each.
On Server PC as and on Remote PC, I have completely dissabled windows firewall.
On router1 I have firewall NAT rules for 443, 500, 4500 ports.
-
- Posts: 286
- Joined: Wed Nov 25, 2020 9:10 am
Re: Obtaining IP
You have two networks both in the 192.168.0.x range. That may cause issues.
-
- Posts: 4
- Joined: Tue Nov 23, 2021 1:36 pm
Re: Obtaining IP
Thanks, Eddie! I`ll try change subnet in my office at this evening.
-
- Posts: 4
- Joined: Tue Nov 23, 2021 1:36 pm