Re: Remote Access and Outlook Web Access on SBS 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

4125 will not respond until a user is authenticated and requests an RDP via
RWW connection. This is secure.

"Greg Kirkpatrick" <GregKirkpatrick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:5374ADA4-7012-4C3D-B961-68FDECBEE91E@xxxxxxxxxxxxxxxx
I'm playing as nice as I can, given the stress my client is putting on me.
No offense intended. I thought I had explained myself well enough, the
first
time; but I could see that more than one had interpreted my remarks
differently than I intended.

I am not using UPnP, and I have configured the DI-524 manually, to allow
traffic on ports 443, 444, 1723, and 4125 to be routed to the server
(192.168.0.2).

Telnet won't work to port 4125, as was mentioned in a previous newgroup
message. As for the other ports, none of them are responding, even though
I
have NO trouble changing settings on the router itself
(http://66.xxx.xxx.xxx:8080).


.

Relevant Pages

  • RE: Remote Desktop & Terminal Services Security
    ... RDP is as secure as your password policy, i.e. if users have strong passwords ... RDP is natively encrypted via 128-bit, ... one port is required for TS to operate, ... I have never seen or heard of a cracked network due to vulnerability in the ...
    (microsoft.public.windows.terminal_services)
  • Re: Created on Access 2003, but.......................
    ... But that's not secure under any scenario, as any port scanner ... Well, you still need a userid, password and database name. ... You're assuming the server remains in a secured configuration. ...
    (comp.databases.ms-access)
  • RE: Server VPN Setup Causes Internal Network to Stop - WIN2K Pro Serve
    ... Nr of workstations to be accessed using RDP ... You'd need to change the default RDP port to anything else but 3389 ports ... years and find myself thrown in to all things Server / System Admin related ...
    (microsoft.public.windows.terminal_services)
  • Re: RWW problem with SBS2003
    ... The only thing we're using RWW for is to connect to the server desktop from ... Generally RDP suits our needs, but we like having RWW for the ... the default RDP port from 3389. ... once port 3389 is in use for one connection from the internet - ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW - RDP Client Connection Problems "The client could not connect to the remote computer...
    ... As a recap I checked the ActiveX "Microsoft RDP ... Client Control file mstscax.dll" mark enabled. ... was trying to use port 4125 has I know that mad.exe will sometimes use ...
    (microsoft.public.windows.server.sbs)