Re: terminal services quirkyness question

I Hope I can figure out what you mean?
When you ssh into your Firewall you are Basically inside your Network
Why it's not working now I don't have a clue
but I'll tell you a way to get around that and direct TS into a server.

If you just want to TS into Pc's without connection to your Firewall you
will have to change the default port that TS listens too...
Example: You connect to your SBS With TS: 213.23.4.15:3389

You have to change the other servers listening Ports so you can redirect
that port to that server
(To change the listen port
http://support.microsoft.com/default.aspx?scid=kb;en-us;q187623 )

So
Server one is 213.23.4.15:3389
Server 2 is 213.23.4.15:3390
Server 3 is 213.23.4.15:3391

Doesn't matter what you make them you can make them in 5's sometimes easier
to remember 3385, 3390, 3395, 3400
Open the Ports in your Firewall and Point them to your servers, in the TS
connection window put the IP and port (At home)
You will have a Quick connection to your servers.

Of course Internally you will have to put server:3390 etc.. But Since TS
Saves the Servers you have in the drop down list its not hard to remember
them.

Of course have a good Password Policy or don't do this.
--
Russ Grover
Small Business IT Support
Portland\Beaverton OR USA
Email: Sales at SmallBusinessITSupport.com
Website: www.SmallBusinessITSupport.com


"tcatt" <tycatt@xxxxxxxxx> wrote in message
news:1119657238.110991.296790@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Folks, howdy from cowtown!
>
> Perhaps someone wiser than myself can answer me something, more or less
> for curiousity's sake I guess. Here's the nutshell:
>
> Corporate network, Windows 2003 SBS domain controller x 2 with Exchange
> 2003 on a Windows XP Pro private network, connected through a NAT
> firewall/VPN router. Now, inside my network (as in, logged into my
> domain) I can remote desktop from any computer to any computer. That's
> fine and dandy.
>
>>>From outside of my network (from home for example), with NAT configured
> in the firewall, the only machine I can successfully connect to is the
> (what used to have been called) my primary domain controller. If I try
> to point the NAT to any other Windows machines, the ones I can connect
> to without a problem from the inside, the attempt fails. "The client
> could not connect to the remote computer. Remote connections might not
> be turned on or the computer might be too busy...."
>
> The funny thing is, this used to work. I would ssh into my firewall and
> feed the private ip address of the workstation I wanted to connect to
> into my NAT rule and blam, I would connect. Now suddenly out of the
> blue it doesn't connect (except to one of my two domain controllers),
> and I can't see why. I've not changed any security settings, and
> (though I may be wrong) I suspect a Microsoft security hotfix to be
> suspect.
>
> Has anyone else encountered anything like this... I googled but no luck
> yet.
>
> While I'm typing away to this group, I'm trying to determine why it's
> recommended not to run redundant exchange servers.. I just found this
> out this morning and it seems to defeat the purpose of having redundant
> servers. The Microsoft technician I spoke with told me that in the
> event of an emergency I could/should then install exchange onto the
> "secondary" domain controller, load the users' mailboxes and would be
> good to go from there but that seems like a pretty ineffective way of
> maintaining corporate email... ?
>
> Well anyways, thank in advance for any thoughts. :)
>


.

Relevant Pages

  • RE: Secure Network Design (DMZ, LAN, etc)
    ... you'll see that their both on the same subnet. ... It has a port for the trusted network and a port ... Our firewall handles NAT. ... > servers, wouldn't it require a public IP and therefore be somewhat ...
    (Security-Basics)
  • Re: Turning on Media Sharing in WMP11
    ... I believe it forms quite a reasonable network media device. ... Turning on SSDP (it was disabled as was uPnP) to Manual and then UPnP ... If there is a firewall, or NAT, built into your ... You need to open port s: ...
    (microsoft.public.windowsmedia.player)
  • RE: [fw-wiz] Security Audit and Priorities
    ... Learn your network. ... - Linux Security Cookbook ... Building Secure Servers with Linux ... It's one thing to be a firewall admin and write ...
    (Firewall-Wizards)
  • Re: May need to move from SBS because of connection issues
    ... Just to make sure you are clear regarding port 4125, ... access remote systems and you are behind a firewall on a non-SBS network, ... established that RWW worked TO your SBS network from outside. ... have been proof that the required ports were forwarded to the SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Help In network configuration.
    ... port of a router. ... 2] I will run a cable from Internal Port of router to the ... external port of firewall. ... Servers Switch. ...
    (microsoft.public.win2000.networking)