|
|
The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024
|
|
Latest message you have seen: Re: HA Scotland thanks
|
[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: "Chris Bond" <chris@xxxxxxx>
- Date: Tue, 25 Nov 2003 20:33:37 -0000
- Mailing-list: list ukha_d@xxxxxxx; contact
ukha_d-owner@xxxxxxx
- Reply-to: ukha_d@xxxxxxx
> I'm not a VPN or MS expert but do play with routing a fair bit. To
me its
> sounds more like a missing route issue than a subnet mask.
On the server its perfect i can ping/connect to both segments its
only when VPN users come in.
> Is the VPN server the only Device routing between the 192.168.1 and
> 192.168.2 subnets (for normal devices) or is there other
infrastructure
> doing that ?
Effectively its all thats routing - theres other firewalls etc in
place there but nothing that isnt stopping it - its physically on
the VPN server the problem lies.
> Can Non VPN Devices on 192.168.2.x can ping devices on
192.168.1.x ? (otherv than the server itself)
No as they dont have two network cards in each workstation - only
the servers have them in so can only route from the server.
> Can the VPN Client ping ....
> The VPN server on its 192.168.2.x address ?
Yes
> The VPN server on its 192.168.1.x address ?
No
> Other Devices on 192.168.2.x ?
Yes
> Other Devices on 192.168.1.x ?
No
> anything! ?
Yes
This is still driving me crazy =)
Home |
Main Index |
Thread Index
|
|