I need to be able to connect from a pc in a Small Business Server network to
a pc in a different Small Business Server network. (One owner, two mirror
companies with no legal ties, each with their own SBS network running Win2K
server, ISA 2K server)

I can connect directly to any computer from any computer as long as one is
not inside a network, but can't conect if both are in Lans. I don't know if
ISA can port forward, but if it can it has to do it cleverly, because I
still need to be able to Remote to any computer in either Lan when I'm
administering from home.

If my question is not clear, please give me some guidance on which part is
hard to understand.

Thanks, Bob Graham

Bob Graham wrote:
> I need to be able to connect from a pc in a Small Business Server
> network to a pc in a different Small Business Server network. (One
> owner, two mirror companies with no legal ties, each with their own
> SBS network running Win2K server, ISA 2K server)
>
> I can connect directly to any computer from any computer as long as
> one is not inside a network, but can't conect if both are in Lans. I
> don't know if ISA can port forward, but if it can it has to do it
> cleverly, because I still need to be able to Remote to any computer
> in either Lan when I'm administering from home.
>
> If my question is not clear, please give me some guidance on which
> part is hard to understand.

Setup a VPN at each site - connect to that VPN to get on the private network
and then you can treat it as if you were there.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Hmmm, I've already done that, I think it used to work trouble-free when XP was first released, but then stopped after some security updates.

For example: Computer A in Network A makes a VPN connection to Server B in network b at 66.88.99.101

VPN connect successfull, can browse remote files etc.

Computer A in Network A Opens remote desktop and tries to connect to WorkStationB1.NetworkB.local

No joy, connection cannot be established.

This approach works fine from outside world to computer WorkStationB1 in Network B

Bob Graham

"Shenan Stanley" <newshelper@gmail.com> wrote in message news:ee8fHx84FHA.696@TK2MSFTNGP09.phx.gbl...

>
> Setup a VPN at each site - connect to that VPN to get on the private network
> and then you can treat it as if you were there.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>

OK, I found the answer for any who care:

On ISA server, create a Protocol definiton that defines an inbound tcp port,
say 3390, and then create a web publishing rule that says what computer to
send incoming calls to that port to.

On the PC, go into the registry and change what port RDP listens on to the
port you chose earlier (3390). Can be any not commonly designated port. 3390
happens to be one digit up from 3389, the standard rdp port.

If the pc has XP firewall enabled, add a new open port to match.

Now you can reach that PC from inside the lan at: <computer name>:3390
Or from the outside world at <External IP of Isa server machine>:3390

Works like a charm. Now as a bonus, when I connect to my machine from my
home pc, I no longer need to vpn to the server first.

Bob Graham


"Shenan Stanley" <newshelper@gmail.com> wrote in message
news:ee8fHx84FHA.696@TK2MSFTNGP09.phx.gbl...

> Setup a VPN at each site - connect to that VPN to get on the private
> network and then you can treat it as if you were there.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>