Re: Using Remote Desktop From an SBS Domain

I have looked at that article again today and also read through it
yesterday. It goes into detail about how to set the host computer up (the
machine who's desktop I'm wanting to connect to) but doesn't say much about
ports or settings on the client end. I have no control over the host end but
just wanted to be sure I have things set correctly on the client end to
allow this to work.

Thanks
Jeff


"Ritch_DA" <RitchDA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:605F7F3E-475B-446B-B179-DA125DD90ECB@xxxxxxxxxxxxxxxx
From what I remember when you install tsweb on your host PC you can change
the port number you connect to from 80 (default) to a port of your choice.
Then obviously create the port forward in your router on your chosen port
to
the appropriate IP (local PC's IP) then connect to it in internet explorer
using the following syntax: http://ipaddress:port/tsweb/

You still need to open 3389.

Have a careful read through those instructions I linked to, that article
explains exactly how to setup what you are trying to do.

-----------------------------------------------------------------
"Jeff Teel" wrote:

It would appear that way but I'm not sure just how to change that. This
machine is on a University network and has a public IP address assigned
to
it. I have tried using the IP address in the Computer: box as well as the
actual domain/computer name of the machine with the same results. You
sparked a question in my mind about installing tsweb on the host pc
though.
Am I assuming correctly that connecting using a web browser through ts
still
uses port 3389? Either way (using a web browser or the Remote Desktop
client) does it require any ports to be open on the client end?

Thanks
Jeff

"Ritch_DA" <RitchDA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:74C2DFCE-73F1-4B09-918F-BF2A43CA36BA@xxxxxxxxxxxxxxxx
Hi Jeff

I read through very quickly but it sounds like you are connecting to
the
wrong machine.

Good solution is to install tsweb on the host machine, change the port
to
something other than 3389 then connect to the machine via your browser.

Here's all the info you need:
http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx

Hope that helps

"Jeff Teel" wrote:

I have tested it and I get the message "The system could not log you
on.
Make sure your user name and domain are correct, then type your
password
again. Letters in the password must be typed in the correct case." I
am
positive that the username and password are being put in correctly.
There
are a couple of things that make me question settings. One, when I get
the
message The system could not log you on........ my workstation appears
to
be
trying to logon to my SBS. The desktop picture thats on my server
shows
and
the Windows Server logon screen appears for me to re-enter the
credentials.
I'm also getting logon failure errors in my security log from the
server.
I
can however see the connection take place in ISA

Logon Failure:
Reason: Unknown user name or bad password
User Name: test
Domain: network
Logon Type: 10
Logon Process: User32
Authentication Package: Negotiate
Workstation Name: SERVER
Caller User Name: SERVER$
Caller Domain: teelnet
Caller Logon ID: (0x0,0x3E7)
Caller Process ID: 5296
Transited Services: -
Source Network Address: 10.10.2.4
Source Port: 60818

Some history about my Internet connection. I have a fixed wireless
Internet
provider. The provider maintains a large wireless LAN that uses
private
IP
addresses.They have access points located on towers around the area
that
a
device from my location looks at. The Source Network Address:
10.10.2.4
is
the wireless IP address side of my router. In short my router has two
NIC's,
the 10.10.2.4 (fixed wireles side) and 192.168.0.x side.

Thanks
Jeff


"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:OXrFkqQ8HHA.5012@xxxxxxxxxxxxxxxxxxxxxxx
did you test it? did it work?

--
Claus
"Jeff Teel" <jdteel@RMoveThis sugardog.com> wrote in message
news:%23NvyCJP8HHA.5984@xxxxxxxxxxxxxxxxxxxxxxx
I am attempting to connect to a Windows XP Pro PC on a totally
different
network from a workstation on my SBS network. I have SBS 2003 SP1
with
ISA
2004. The PC that I'm trying to connect to does have a static IP
address
and I'm using that for the Computer Name in the Remote Desktop
Connection
client. I used "telnet xxx.xxx.xxx.xxx 3389" to see if the remote
workstation was listening on the correct port and it is. My
question,
are
there any ISA adjustments needed on my network in order for me to
Remote
Desktop out to another XP Pro machine on a different network over
the
Internet? I'm using the c:\windows\system32\mstsc.exe application to
make
the connection. The remote host does not have Remote Desktop Web
Connection installed on it.

Thanks
Jeff











.

Relevant Pages

  • Re: pre-scanning for vulnerability scans?
    ... If by source, you're refering to the network you are testing from, you ... dictionary file for finding host names. ... full port SYN scan on detected hosts ... Audit your website security with Acunetix Web Vulnerability Scanner: ...
    (Pen-Test)
  • Re: Should I configure a firewall to allow multicast?
    ... firewall is blocking various hosts to 192.168.1.255 port 138. ... network running from 192.168.1.0 through 192.168.1.255 which would ... broadcast address - received by every host on the subnet. ...
    (comp.security.firewalls)
  • Re: Using Remote Desktop From an SBS Domain
    ... Then obviously create the port forward in your router on your chosen port to ... machine is on a University network and has a public IP address assigned to ... trying to logon to my SBS. ... Some history about my Internet connection. ...
    (microsoft.public.windows.server.sbs)
  • RE: FW: Legal? Road Runner proactive scanning.[Scanned]
    ... port scan on TCP 25? ... If your host is on the internet I consider it public and knocking on ... Port scanning is not an attack it is probe. ... someone else's network without permission. ...
    (Security-Basics)
  • Re: Can send but dont receive emails
    ... Connecting To XX.XXX.XX.XXX Could not open connection to ... TCP port 25? ... >> network. ... >> I have a domain host where I forward requests for my ...
    (microsoft.public.exchange.connectivity)