|
|
The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024
|
|
Latest message you have seen: RE: COMPLETELY OT!! For those who liked pingu!!
|
[Date Prev][Date
Next][Thread Prev][Thread Next][Date
Index][Thread Index]
OT: Win2003 Routing/VPN Issue
- To: ukha_d@xxxxxxx
- Subject: OT: Win2003 Routing/VPN Issue
- From: "Chris Bond" <chris@xxxxxxx>
- Date: Mon, 24 Nov 2003 16:23:21 -0000
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
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!
Home |
Main Index |
Thread Index
|
|