In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!
Netgear FVS318 with Client Access Software to SBS 2003
We have a Netgear FVS318 connected to one LAN card on a server (SBS 2003 Standard). The other LAN card in the server connects to the internal LAN.
The FVS has been configured for internet access which works as intended. It is on a 192.168.10.1 (255.255.255.0) address. The server LAN IP is 10.0.1.1 (255.255.255.0).
We have installed the Netgear client access software on a laptop and can connect to the FVS from any remote location. We don't seem to be able to connect to the server which we do need for email via Exchange.
Netgear support suggested setting a static route on the FVS but either we aren't setting it correctly or something else is being missed.
Any help to resolve this would be greatly appreciated.
The FVS has been configured for internet access which works as intended. It is on a 192.168.10.1 (255.255.255.0) address. The server LAN IP is 10.0.1.1 (255.255.255.0).
We have installed the Netgear client access software on a laptop and can connect to the FVS from any remote location. We don't seem to be able to connect to the server which we do need for email via Exchange.
Netgear support suggested setting a static route on the FVS but either we aren't setting it correctly or something else is being missed.
Any help to resolve this would be greatly appreciated.
Asked:
5-
5
1 Solution
Thanks for the response.
The internal network is on 10.0.1.x. It is on a different range to the internet connection 192.168.10.x as we have some additional wireless access points which only give internet access to some users. We don't want them browsing the internal network.
From what you've written, if we change the internal 10. range to match the 192. range, that will solve the remote client issue ?
The internal network is on 10.0.1.x. It is on a different range to the internet connection 192.168.10.x as we have some additional wireless access points which only give internet access to some users. We don't want them browsing the internal network.
From what you've written, if we change the internal 10. range to match the 192. range, that will solve the remote client issue ?
Wait.
So you have there an DMZ in 192.168.10.x and an LAN on 10.0.1.x.
Your remote clients get an IP address from Netgear client. If that address is 192.168.10.x you need to implement a communication path between DMZ and LAN.
So you have there an DMZ in 192.168.10.x and an LAN on 10.0.1.x.
Your remote clients get an IP address from Netgear client. If that address is 192.168.10.x you need to implement a communication path between DMZ and LAN.
To clarify the remote address. The Netgear client software does obtain an IP of 10.0.1.45 but the SM is 255.255.255.255. Our internal LAN is 255.255.255.0 so I assume part of the problem lies there.
How would we implement the communication path between the DMZ and LAN ? Is that an equivalent to the static route on the FVS318 ? I have tried various IP combinations in the static route but they don't help.
Thanks again for the help.
How would we implement the communication path between the DMZ and LAN ? Is that an equivalent to the static route on the FVS318 ? I have tried various IP combinations in the static route but they don't help.
Thanks again for the help.
That is weird.
I read the manual and I don't undestood why they need another IP class for VPN. Anyway You can follow the manual intruction and put in the VPN IP (that in manual is 192.168.2.x) 10.0.2.x, but on the server you need to add a static route that will send all trafic for this IP class to netgear.
something like route add 10.0.2.0 mask 255.255.255.0 10.0.1.serverIP.
Dan
I read the manual and I don't undestood why they need another IP class for VPN. Anyway You can follow the manual intruction and put in the VPN IP (that in manual is 192.168.2.x) 10.0.2.x, but on the server you need to add a static route that will send all trafic for this IP class to netgear.
something like route add 10.0.2.0 mask 255.255.255.0 10.0.1.serverIP.
Dan
I have added a route on the server but it hasn't made any difference.
If changing the server's internal LAN IP range to match the Netgear will definitely solve this, I can certainly do that. I just want to make sure before changing everything over.
Also, if there is a better way to set all of this up, I would appreciate the advice.
If changing the server's internal LAN IP range to match the Netgear will definitely solve this, I can certainly do that. I just want to make sure before changing everything over.
Also, if there is a better way to set all of this up, I would appreciate the advice.
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.
Join & Write a Comment Already a member? Login.
Featured Post
In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
So your IP for internal network is 192.168.10.x or 10.0.1.x?
I don't undestood why the server has 10.0.1.1and the Netgear 192.168.10.1.
Normaly all your devices that are connected on LAN shoul span an contiguous IP plan. If you use 2 clases then you need an router that will interconect this 2 networks. So even you change the Netgear Internal IP to 10.0.1.x to allow direct communication to server, even you change the server ip to 192.168.10.x. but don't use both...
Dan