Solved

Netgear FVS318 with Client Access Software to SBS 2003

Posted on 2007-11-15
10
390 Views
Last Modified: 2011-09-20
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.
0
Comment
Question by:comsult
  • 5
  • 5
10 Comments
 
LVL 21

Expert Comment

by:dan_blagut
ID: 20288650
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
0
 

Author Comment

by:comsult
ID: 20288741
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 ?
0
 
LVL 21

Expert Comment

by:dan_blagut
ID: 20288760
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.
0
 
LVL 21

Expert Comment

by:dan_blagut
ID: 20288773
What IP address get an remote client when he's connected?
0
 

Author Comment

by:comsult
ID: 20288779
The remote client gets 10.0.1.45.
0
VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

 

Author Comment

by:comsult
ID: 20288887
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.
0
 
LVL 21

Expert Comment

by:dan_blagut
ID: 20289103
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
0
 

Author Comment

by:comsult
ID: 20292038
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.
0
 
LVL 21

Accepted Solution

by:
dan_blagut earned 500 total points
ID: 20296846
Before to change the server IP try to change the IP from one workstation. Then connect to internet using an dial-up and create a VPN to your lan. See if you can connect to this workstation admin share (like \\computername\c$)

Dan
0
 

Author Closing Comment

by:comsult
ID: 31409298
Apologies for the delay and thanks again for your help. We put everything on the same IP range and all now works perfectly.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

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…
A quick step-by-step overview of installing and configuring Carbonite Server Backup.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now