- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Subneting client network for restricted vpn access...
Switches, Hubs, and Modems
1748134
Members
3399
Online
108758
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2005 03:08 AM
02-07-2005 03:08 AM
Subneting client network for restricted vpn access.
Hi all,
I'm not a network guy, just a small systems guy trying to do my best...
I have a small client office housing two companies that currently share a single network connected to a switch thats connected to a router thats connected to a ADSL modem for shared internet access.
I have setup a VPN for one user in each co. to access their office pc's.
I would like to set things up to allow each remote user to access only their pc. The problem is that with only one network and the way the remote vpn client and office router are setup, each remote user can access all of the office pc's on the network. So at this time restricted access is not possible.
The client office has a...
- 1 Linksys BEFSX41 router w/4port switch that supports two vpn tunnels.
- 1 Linksys EZXS16W workgroup switch.
- 1 shared web/email server running WXP Pro.
- 6 user pc's (4 for co.1 and 2 for co.2)
- 2 SSN Sentinel 1.4 remote vpn clients at two users homes.
- We are using class c, 192.168.0.x, nonroutable ip addresses for internal use.
I believe the goal of resticted access can be achieved by dividing the network into three subnets and purchasing some additional routers.
It seems to me that i would have to split the office network into three subnets like...
(internet)
|
[ADSL modem]
|
[router ] 192.168.(0.1)
| | |
/---| | |----\
/ | \
[router]1.1 [router]2.1 [router]3.1
(shared)
(server) (company1) (company2)
- (192.168.0.1) for default gateway router.
- (192.168.1.1) for the shared server subnet.
- (192.168.2.1) for co. 1 subnet.
- (192.168.3.1) for co. 2 subnet.
Am i in the ballpark?
Or can it be done with the equipment that i have by messing around with the router's routing table?
I any case, how do i insure that both companies get the proper access to the web/email server? Would this require making enteries into the routers routing tables?
I hope i'm not asking for too much.
Thanks,
I'm not a network guy, just a small systems guy trying to do my best...
I have a small client office housing two companies that currently share a single network connected to a switch thats connected to a router thats connected to a ADSL modem for shared internet access.
I have setup a VPN for one user in each co. to access their office pc's.
I would like to set things up to allow each remote user to access only their pc. The problem is that with only one network and the way the remote vpn client and office router are setup, each remote user can access all of the office pc's on the network. So at this time restricted access is not possible.
The client office has a...
- 1 Linksys BEFSX41 router w/4port switch that supports two vpn tunnels.
- 1 Linksys EZXS16W workgroup switch.
- 1 shared web/email server running WXP Pro.
- 6 user pc's (4 for co.1 and 2 for co.2)
- 2 SSN Sentinel 1.4 remote vpn clients at two users homes.
- We are using class c, 192.168.0.x, nonroutable ip addresses for internal use.
I believe the goal of resticted access can be achieved by dividing the network into three subnets and purchasing some additional routers.
It seems to me that i would have to split the office network into three subnets like...
(internet)
|
[ADSL modem]
|
[router ] 192.168.(0.1)
| | |
/---| | |----\
/ | \
[router]1.1 [router]2.1 [router]3.1
(shared)
(server) (company1) (company2)
- (192.168.0.1) for default gateway router.
- (192.168.1.1) for the shared server subnet.
- (192.168.2.1) for co. 1 subnet.
- (192.168.3.1) for co. 2 subnet.
Am i in the ballpark?
Or can it be done with the equipment that i have by messing around with the router's routing table?
I any case, how do i insure that both companies get the proper access to the web/email server? Would this require making enteries into the routers routing tables?
I hope i'm not asking for too much.
Thanks,
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2005 08:31 PM
02-07-2005 08:31 PM
Re: Subneting client network for restricted vpn access.
Hi Nelson,
i think, that will not run. What you need is a VLAN setup. So you have to use a 802.1q compliant switch and router. You shall use (as an example) a HP 2512 Switch and a cisco 1711 with the corresponding WIC.
regards
HRE
i think, that will not run. What you need is a VLAN setup. So you have to use a 802.1q compliant switch and router. You shall use (as an example) a HP 2512 Switch and a cisco 1711 with the corresponding WIC.
regards
HRE
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP