Archived from groups: microsoft.public.windowsxp.work_remotely (
More info?)
So you want to dial into the host directly? That is different than connecting through your router
from the public internet...
If the PC has a dial modem attached you can configure XP as a Remote Access Server so you can dial
directly into the PC from work via a telephone connection. Is that what you want to do? If so here
are the instructions to setup XP as a RAS box...
Configure RAS on Windows XP
To configure the computer for incoming connections, follow these steps:
1.. Click Start, and then click Control Panel.
2.. Click Network and Internet Connections, and then click Network Connections.
3.. Double-click Create a new connection to start the New Connection Wizard.
4.. Under Network Connection Type, click Set up an advanced connection, and then click Next.
5.. Click Accept incoming connections, and then click Next.
6.. Click the modem from the list of devices, and then click Next.
7.. Select either of the options to allow Virtual Private Connections, and then click Next.
8.. Click to select the check boxes for the users whom you want to be able to authenticate when
the device connects to the computer, and then click Next.
9.. Make sure that the Internet Protocol (TCP/IP) check box is selected, click Next, and then
click Finish.
You modem should be setup for automatic answer. Check the modem users manual or the manufacturers
web site for help with that...
By the way, you can browse for RDP hosts on a LAN if you follow the instructions I pointed you to in
an earlier reply...
You can't ping the target PC from the public internet because of your firewall/NAT/router... You
also need to call using the public IP of the router, not the private LAN IP...
--
Al Jarvi (MS-MVP Windows Networking)
Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program -
http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...
"Tracy" <Tracy@discussions.microsoft.com> wrote in message
news:E9021BDF-FD53-4C04-847F-1FA0FD618313@microsoft.com...
> Yes. I just found out that although I can't "Browse" the LAN for the Host, I
> can merely type it's network name in the window and it will connect. Port
> 3389 is (and has been) opened (please see prior post), however I cannot
> "ping" host over i-net nor can I connect over i-net. I would like to dial-up
> host over telephone line and not even go on i-net. Know how to do that ?
>
> "Sooner Al" wrote:
>
>> So can you access the desktop from the laptop over the local LAN using the regular (not the web
>> based) Remote Desktop client? If you can't do that, then you will not be able to access the
>> desktop
>> from a remote location.
>>
>>
http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html
>>
>> Any personal firewall software running on the desktop? If so, you also need to open TCP Port 3389
>> or
>> disable the firewall software...
>>
>> --
>> Al Jarvi (MS-MVP Windows Networking)
>>
>> Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
>> The MS-MVP Program -
http://mvp.support.microsoft.com
>> This posting is provided "AS IS" with no warranties, and confers no rights...
>>
>> "Tracy" <Tracy@discussions.microsoft.com> wrote in message
>> news:A0B651D3-CEE9-4384-842C-33207252F162@microsoft.com...
>> > Thanks Al, but IIS is in fact already configured for port 82.
>> >
>> > "Sooner Al" wrote:
>> >
>> >> If you want to use TCP Port 82 for IIS did you also configure IIS for the new port? This old
>> >> thread
>> >> has help for changing the IIS port to something other than the default TCP Port 80...
>> >>
>> >>
http://groups.google.com/groups?hl=en&lr=&c2coff=1&frame=right&th=94cb220b2a08b3da&seekm=uFR9NbFVEHA.3692%40TK2MSFTNGP09.phx.gbl#link3
>> >>
>> >> Use the form http://PC_Address:82/tsweb/
>> >>
>> >> ....to call...
>> >>
>> >> Once you get this working over the private LAN, then be aware you also need to forward both
>> >> the
>> >> new
>> >> IIS port, TCP Port 82 in your case, and TCP Port 3389 through the router. See this page for
>> >> help
>> >> with that...
>> >>
>> >>
http://www.portforward.com/routers.htm
>> >>
>> >> Personally, I see no advantage in your case to using the web based access method. It simply
>> >> complicates the issue, IMHO. Try connecting with the normal Remote Desktop client to make sure
>> >> that
>> >> works then, if you still want to, try the web based method...
>> >>
>> >> --
>> >> Al Jarvi (MS-MVP Windows Networking)
>> >>
>> >> Please post *ALL* questions and replies to the news group for the mutual benefit of all of
>> >> us...
>> >> The MS-MVP Program -
http://mvp.support.microsoft.com
>> >> This posting is provided "AS IS" with no warranties, and confers no rights...
>> >>
>> >> "Tracy" <Tracy@discussions.microsoft.com> wrote in message
>> >> news:EFF98141-24CB-464D-AA31-1C60C335AE4B@microsoft.com...
>> >> >I have CPU1 (work) XP PRO on LAN with router & DSL modem, laptop @ home
>> >> > (running XP Home) using dial-up. I have red everything applicable to my issue
>> >> > posted here & still haven't gotten Remote Desktop working AT ALL.
>> >> >
>> >> > I HAVE done the following to the HOST (work) computer:
>> >> > -Checked the box in System Properties to Allow users to connect to this
>> >> > (HOST) computer.
>> >> > -Selected Remote Desktop Users (complete with passwords)
>> >> > -Used Windows Add/Remove programs to add Internet Information Services
>> >> > Remote Desktop Web Connection
>> >> > -Logged onto router and port forwarded 3389 to host 192.168.0.2 (host on LAN)
>> >> > -Also port forwarded 82 to same (NOT 80 for "security")
>> >> >
>> >> > I HAVE done the following on the LAPTOP (client) computer:
>> >> >
>> >> > When I try to connect using the ip of the router (confirmed with
>> >> > "Whatsmyip.com"), what I get is the standard "The client could not connect to
>> >> > the remote computer. Remote connections might not be enabled or the computer
>> >> > might be too busy..."
>> >> >
>> >> > When I try to connect on the LAN using the "Browse for Computers" I get
>> >> > The WORKGROUP domain/workgroup does bot contain any Terminal servers.
>> >> >
>> >> > I have been working on this for 4 days now, day 2 I could log onto RD while
>> >> > on LAN, but not internet. Tonight I added IIS and can't do squat (except get
>> >> > remarkably frustrated).
>> >> > Ideally I would like to connect with dial-up from laptop directly to
>> >> > dial-up modem in host (work) computer and use RD, but don't know if that's
>> >> > supported. Ultimately use RD to utilize faster web access through DSL @ work.
>> >> > Thanks in advance for all of your help and expertise.
>> >> > Tracy
>> >> >
>> >> > "Russ" wrote:
>> >> >
>> >> >> I have set up my Office computer for remote desktop. It is using LAN and
>> >> >> proxy. I am trying to connect from home (dial up) but no sucess. I tried to
>> >> >> ping my office computer but no reply back. ( I have set up all the necessary
>> >> >> settings on both computers)
>> >> >>
>> >> >> Any help appreciated
>> >> >>
>> >>
>> >>
>>
>>
Facebook
Twitter
Instagram