Re: Remote Desktop to Other PC systems on the Network from Remote
- From: Reodd <Reodd@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 8 May 2006 08:54:02 -0700
dont think that the routes used would be of use on the branch office
machines but I have added a route destination (any destination matching the
IP 192.168.16.0 255.255.255.0 (local LAN) use Gateway 10.10.2.254 (internal
interface of the PIX at branch)
No result....I think that we are trying to be to clever.....I feel that this
is a simple one but I just cant see it.
Remember when I tunnel in from home using the SBS VPN I can remote control
any and all XP machnes..
The issue lies with Traffic coming via the PIX (VPN) router( not the PC at
the Branch)....If I could ascertain what the RDP protocol was doing over the
course of its journey I may be in a better position to fix this.
Do I need to have the external interface of the PIX at Branch side somewhere
on the ISA with a rule allowing all traffic?
--
Regards Reodd
"Reodd" wrote:
Many Thanks,.
Sorry ..Yes my 1720 has an internal interface on the LAN.
I have added the remote network ranges to the "Internal" network definition
already...Had to do this to kick start any form of communications anyway..But
this does not resolve the RDP thinggy
I also already have 2 persistent routes (using route print) these identify
that any destination traffic for 10.10.2.0 and 10.10.3.0 will use the gateway
192.168.16.1 (1720 Internal Interface) ( as opposed to the 192.168.16.2
gateway of the SBS/ISA box)
Just to clarify all remote and local connectivity seems OK. systems at
remote sites can see the shared resources on the head office LAN they can
even (with the correct username and password) RDP into the headoffice server.
I agree that somewhere along the line the RDP is being blocked but in which
direction and how to resolve still escape me.
could there be a need for a firewall rule or am I missing something more
fundemental.
--
Regards Reodd
"ZVR" wrote:
Connects to Cisco 1720 Router This manages the VPN traffic. (blocks
nothing
else just has a dedicated link via routes to the other sites.)
You still didn't clarify whether the 1720 has an "internal" interface in the
LAN. It probably has, and I will respond assuming this is the case, just
wanted to positively confirm this.
Everything was working very well before I installed ISA 2004. (So this is
where the issue lies)
OK, it seems like you have an issue where packets from the remote sites
arrive at the computers on the HQ LAN but reply packets never make it back.
I assume all your computers in the HQ LAN have the default gateway set to
ISA. If this is the case then you need to:
1) Include the subnets at the remote offices in the definition of the
"Internal" network object on the ISA server.
2) Create static routes on the ISA machine that forward all traffic
destinated to the remote networks to the "internal" interface of the Cisco
1720.
Good luck,
Virgil
- Follow-Ups:
- References:
- Prev by Date: Re: Frequent requests to ports 35000 - 37000
- Next by Date: Re: Dell PowerEdge 1850 suitable for ISA?
- Previous by thread: Re: Remote Desktop to Other PC systems on the Network from Remote
- Next by thread: Re: Remote Desktop to Other PC systems on the Network from Remote
- Index(es):
Relevant Pages
|
