> On Jun 19, 3:33 am, "Russ Grover \(SBITS.Biz\)"
> <supp...[ at ]REMOVETHIS.SBITS.Biz> wrote:
>> Blenky,
>>
>> in addition to the others suggestions (Opening Port 3389)
>> put /console on the end of the command line of RDP
>> Like So:
>> %SystemRoot%\system32\mstsc.exe /console
>>
>> It will allow you to see the screen as though sitting in front of the
>> server
>> Great if you want to watch automated backups or some other automated
>> process.
>>
>> And of course PLEASE follow Secure Password Policies.
>> (I set Lockout to 5 missed login attempts on clients and 3 on my own
>> server)
>> Russ
>>
>> --
>>
>> Russell Grover
>> SBITS.Biz
>> Microsoft Certified Small Business Specialist.
>> MCP, MCPS, MCNPS, (MCP-SBS)
>> support [ at ] SBITS.Biz
>> Remote SBS2003 Support
http://www.SBITS.Biz>>
>> "Blenky" <sblenkh...[ at ]gmail.com> wrote in message
>>
>> news:1182181857.204691.3380[ at ]q75g2000hsh.googlegroups.com...
>>
>>
>>
>>
>>
>> > Should I be able to RDP directly to my server from the outside world
>> > without going through Remote Workspace?? I seem to be able to connect
>> > directly to the server via RDP by just using the domain or IP address
>> > from the outside world... that doesn't seem quite right!
>>
>> > Thanks,
>> > Sean- Hide quoted text -
>>
>> - Show quoted text -
>
>
> It just seems insecure to have the ability to RDP directly to my
> server just by putting in the IP address or the domain for our
> server. I disabled port 3389 on our firewall and left 443 and 4125
> open and now RWW does not work to connect to the server. So must I
> keep 3389 open on the firewall??
>
> Thanks,
> Sean
>