Re: Looking for W2K3 to route back to imcoming gateway
- From: "Mike Spike" <Mike@xxxxxxxxxxxxxxxx>
- Date: Thu, 20 Jul 2006 15:39:03 +0100
Just one short point.
If you are using that 3389 for RemoteDesktop / Terminal service connections
I would change it to diffrent port because of the nature of the service.
You can do this by changing the PortNumber Key in the registry.
And then appending that port to the clients connection information
In IP:Port# format.
Of course if it is not meant to be public facing then ignore this!
Mike.
"Troppy" <Troppy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3644E8E5-C4A7-48E6-8E06-CBDD435EC160@xxxxxxxxxxxxxxxx
Hi,
We have a W2K3 server (say 192.168.1.20) which is on a local LAN.
There are two internet connections, both running Cisco routers,
192.168.1.254 (the main one) and 192.168.1.253 (the backup/incoming mail
one).
When we use the .254 cisco to forward ports from outside (ie 25 or 3389)
to
the server, everything works OK. If we do the same with the backup
connection
(.253) the connection from outside to either 25 or 3389 does not work.
I think this is because the W2K3 server is handed to originating public IP
address when a connection is made to either 25 or 3389 and by default goes
back out by .254.
Is there any way to make the W2K3 Server send the packets back through the
gateway that the connection came through, rather than always going out by
the
default connection?
Thanks for your help - and I hope I've explained it OK!
Kind regards,
Paul
.
- Prev by Date: Re: two nics, one ip
- Next by Date: Re: Sharing files between Domain / Workgroup
- Previous by thread: How fast of a connection do I need?
- Next by thread: Win2K3 - Multiple IP Addresses Bound to One NIC
- Index(es):
Relevant Pages
|
