Hi there I hope someone can help with my problem which is driving me crazy.
My situation is as follows:
Our office LAN sits in a netowrk range 192.168.7.0 subnet 255.255.255.0
We have one machine connected on this LAN that acts as a file server. Its IP address is 192.168.7.4
The DGFV338 acts as ADSL modem, router and WLAN access point. Its IP address is 192.168.7.1
We have no AD, WINS, DNS servers etc. on this LAN - it is very basic
A number of us work remotely. When we're in the office we connect via wi-fi, get allocated a DHCP address from the DGFV338 in the range 192.168.7.50 to 192.168.7.100. Everything works beautifully. While connected via Wi-Fi (or indeed wired ethernet) we access the file server via \\192.168.7.4\<sharename> We can also ping 192.168.7.4 successfully.
This Netgear replaced a Draytek SOHO router. While out of the office we simply used Windows built in VPN client to establish a connection and we could ping the file server and access the shares in exactly the same way as when on the LAN. It was very simple.
With the new Netgear in place I set up one of the laptops with the ProSafe client. This laptop then connects to the internet when out of the office via a number of different means, but usually always behind a router, whether in a hotspot or at home.
I decided the modeconfig option looked best for our needs and I understood the principle a little better so I went down the route and followed the guide here:
http://home.comcast.net/~uploader/vpn/Tutorials/FVX538v2 ModeConfig Setup.pdf
I set it up so all my screens look exactly the same as that (including the modeconfig IP address allocation of 192.168.110.1 - 5). Exceptions included:
- No WINS or DNS entries in the modeconfig entry (we don't have anything on the LAN doing this).
- WAN address for the office changed from 1.1.1.1 to our real static Internet facing IP address
- Used our own pre-shared key
Now when I connect the laptop to the internet and choose to connect my ProSafe client it goes through the motions and connects just fine. I looked at the logs on the client and they matched the ones in the tutorial except for the "Received DNS..." entry, which is to be expected as I did not specify one in modeconfig.
The machine says it is connected OK, log is good and connection montior shows the connection and the icon in the task bar has the word "on" showing. All good.
But try as I might, I cannot ping our file server on 192.168.7.4, nor access any of its drives. I also cannot ping or browse the DGFV338 itself on 192.168.7.1 (although I'm not sure if I should be able to so less worried about this).
So what am I doing wrong? I feel it is something simple. Should I set the DGFV338's IP address (192.168.7.1) as the DNS server entry in modeconfig, as that is the only thing on the LAN that acts as a DNS server of sorts, pasing through the ISPs? All help gratefully appreciated.
For reference, if it is relevant, the most common scenario for this laptop (and the one I am doing most of the testing with) when remote is sat behind a NAT router on a home ADSL connection. ADSL receives a dynamic random IP from the ISP and the laptop sits behind it on the network with an IP address of 192.168.0.x and subnet 255.255.255.0 although clearly it be connecting from any one of a number of different scenarios depending on where in the world we are.
My situation is as follows:
Our office LAN sits in a netowrk range 192.168.7.0 subnet 255.255.255.0
We have one machine connected on this LAN that acts as a file server. Its IP address is 192.168.7.4
The DGFV338 acts as ADSL modem, router and WLAN access point. Its IP address is 192.168.7.1
We have no AD, WINS, DNS servers etc. on this LAN - it is very basic
A number of us work remotely. When we're in the office we connect via wi-fi, get allocated a DHCP address from the DGFV338 in the range 192.168.7.50 to 192.168.7.100. Everything works beautifully. While connected via Wi-Fi (or indeed wired ethernet) we access the file server via \\192.168.7.4\<sharename> We can also ping 192.168.7.4 successfully.
This Netgear replaced a Draytek SOHO router. While out of the office we simply used Windows built in VPN client to establish a connection and we could ping the file server and access the shares in exactly the same way as when on the LAN. It was very simple.
With the new Netgear in place I set up one of the laptops with the ProSafe client. This laptop then connects to the internet when out of the office via a number of different means, but usually always behind a router, whether in a hotspot or at home.
I decided the modeconfig option looked best for our needs and I understood the principle a little better so I went down the route and followed the guide here:
http://home.comcast.net/~uploader/vpn/Tutorials/FVX538v2 ModeConfig Setup.pdf
I set it up so all my screens look exactly the same as that (including the modeconfig IP address allocation of 192.168.110.1 - 5). Exceptions included:
- No WINS or DNS entries in the modeconfig entry (we don't have anything on the LAN doing this).
- WAN address for the office changed from 1.1.1.1 to our real static Internet facing IP address
- Used our own pre-shared key
Now when I connect the laptop to the internet and choose to connect my ProSafe client it goes through the motions and connects just fine. I looked at the logs on the client and they matched the ones in the tutorial except for the "Received DNS..." entry, which is to be expected as I did not specify one in modeconfig.
The machine says it is connected OK, log is good and connection montior shows the connection and the icon in the task bar has the word "on" showing. All good.
But try as I might, I cannot ping our file server on 192.168.7.4, nor access any of its drives. I also cannot ping or browse the DGFV338 itself on 192.168.7.1 (although I'm not sure if I should be able to so less worried about this).
So what am I doing wrong? I feel it is something simple. Should I set the DGFV338's IP address (192.168.7.1) as the DNS server entry in modeconfig, as that is the only thing on the LAN that acts as a DNS server of sorts, pasing through the ISPs? All help gratefully appreciated.
For reference, if it is relevant, the most common scenario for this laptop (and the one I am doing most of the testing with) when remote is sat behind a NAT router on a home ADSL connection. ADSL receives a dynamic random IP from the ISP and the laptop sits behind it on the network with an IP address of 192.168.0.x and subnet 255.255.255.0 although clearly it be connecting from any one of a number of different scenarios depending on where in the world we are.