Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!
Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!
Act now. This offer ends July 14, 2017.
Course Of The Month
6 days, left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Netgear FVS318 with Client Access Software to SBS 2003
Posted on 2007-11-15
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.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
5-
5
10 Comments
Hi
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
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
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.
Featured Post
Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Hi there,
This article summarizes what you need if you are going to set up your home or small business Network Attached Storage (NAS) to be accessible from the internet. Of course there are configuration differences based on your NAS or router ma…
I work for a company that primarily works with small businesses as their outsourced IT vendor. As such the majority of these customers utilize some version of Small Business Server. Due to the economics of running a small business, many of these cus…
This is a high-level webinar that covers the history of enterprise open source database use. It addresses both the advantages companies see in using open source database technologies, as well as the fears and reservations they might have.
In this…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Suggested Courses
Course of the Month6 days, left to enroll
705 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.