|
The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024
|
Latest message you have seen: Fw: Re: OT : Building Costs (It will house HA, so mebe not OT!) |
[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
RE: OT: Win2003 Routing/VPN Issue
- To: <ukha_d@xxxxxxx>
- Subject: RE: OT: Win2003 Routing/VPN Issue
- From: "Dean Smith" <ukha@xxxxxxx>
- Date: Tue, 25 Nov 2003 13:15:58 -0000
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
Chris
What is the DHCP pool ? (is it on the 192.168.2 segment)
If that segment is used only for VPN clients why have you got a Netwrok
card
for it ?
What is the default gateway for the devices on the 192.168.1.x subnet ? If
its anything other than the VPN server, do those devices have static routes
for the 192.168.2.x subnet via the VPN server ?
Dean
-----Original Message-----
From: Chris Bond [mailto:chris@xxxxxxx]
Sent: 24 November 2003 16:23
To: ukha_d@xxxxxxx
Subject: [ukha_d] OT: Win2003 Routing/VPN Issue
Got an interesting one here cant seem to get a working solution
round it.
Got a Windows 2003 Server which is the AD Controller acting as VPN
Server.
The machine has two networks cards in say 192.168.2.2 being the
primary network with no default gateway. The second network card is
192.168.1.2 with a default gateway of 192.168.1.254.
The VPN Server is bound to the 192.168.2.2 interface and uses dhcp
to allocate the addresses.
What we effectively need to do is allow VPN users on 192.168.2.x
segment allowed access to 192.168.1.x segment. From the server
itself you can ping both segments and connect to both networks its
only when you vpn in it stops access to the other segement.
Any ideas? this is driving me nuts!
UKHA 2004: 15th and 16th May 2004
http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe: ukha_d-subscribe@xxxxxxx
Unsubscribe: ukha_d-unsubscribe@xxxxxxx
List owner: ukha_d-owner@xxxxxxx
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Home |
Main Index |
Thread Index
|
|