The UK Home Automation Archive

Archive Home

Group Home

Search Archive
Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

[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: "Shaf Ali" <shaf@xxxxxxx>
Date: Tue, 25 Nov 2003 00:14:20 -0000
Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
References: <bptb9p+1pa9@xxxxxxx>
Reply-to: ukha_d@xxxxxxx

> 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!

Silly solutions must be tried first be4 divulging into vpn and routing
........... Is the netmask = 255.255.0.0 for clients on both segments ?

References:
- OT: Win2003 Routing/VPN Issue
  - From: "Chris Bond" <chris@xxxxxxx>

Prev by Date: [OT] Any Cheap Disk Deals
Next by Date: Re: OT: Win2003 Routing/VPN Issue
Previous by thread: OT: Win2003 Routing/VPN Issue
Next by thread: Re: OT: Win2003 Routing/VPN Issue
Index(es):
- Date
- Thread

Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.