Archived from groups: microsoft.public.windowsxp.work_remotely (
More info?)
If you can not connect over the private LAN to the TS you changed the listening port on, from
another PC on the LAN, then its a problem with...
1. The TS not being configured for the new port correctly.
2. The TS not being configured correctly.
3. Not using the correct IP for the TS.
4. Some other problem.
Note that to test this you can *NOT* be on the private LAN and using the public IP of the router. To
test properly you need to be at a remote location, or dialup to the internet, in order to use the
public IP of the router.
--
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...
"Connie Gibson" <conniegibson@hchd.net> wrote in message
news:C-idnRTaJeeBkgzdRVn-tw@amaonline.com...
> No does not work over a private lan, I have one TS on port 3389 and I can
> use it on the lan or wan works fine. I set up a second TS and changed the
> port to 3390 on it and port forwarding in the linksys router the same as the
> port 3389 entry and the 3390 TS will not connect.
> I am using one public IP in the router and wanting to connect through rdt
> with the adress
![:p :p]()
ort number on 2 different machines. Any suggestions? I am
> using a linksys BEFSR11.
>
> TIA
>
>
>
>
> "Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in message
> news:uGRa64eLEHA.3348@TK2MSFTNGP09.phx.gbl...
>> Try this telnet test on Port 3390 to see if you can pinpoint the problem.
>>
>>
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628
>>
>> Does this work over the private LAN?
>>
>> --
>> 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...
>>
>> "Connie Gibson" <conniegibson@hchd.net> wrote in message
>> news:0v-dndMVuNRZnAzdRVn-sw@amaonline.com...
>> >I am usinf a linksys router and have this configured to the specs from
> the
>> > link sooner al posted. I am running 2 windows 2000 servers with terminal
>> > services. For some reason I cannot get the computer listening on 3390
> to
>> > respond. Any suggestions?
>> >
>> >
>> >
>> >
>> >
>> > "Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in message
>> > news
![:o :o]()
2MWGWdLEHA.644@tk2msftngp13.phx.gbl...
>> >> Did you also configure the XP Internet Connection Firewall (ICF), if
>> > enabled, or other personal
>> >> firewall to forwarded TCP Port 1002 to PC2?
>> >>
>> >>
http://members.cox.net/ajarvi/RemoteDesktop/Multiple_PC...
>> >>
>> >> --
>> >> 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...
>> >>
>> >> "Alex Lee" <simplitia@yahoo.com> wrote in message
>> >> news:21ba229.0404282154.6b5ffffd@posting.google.com...
>> >> > Ok my story is kind of complicated.
>> >> >
>> >> > Basically I have two computer where computer1 is connected to the
>> >> > internet and allows ICS (internet connection sharing) for computer2.
>> >> > Both computers are running xp-pro.
>> >> >
>> >> > So far I change the port for "remote desktop" on computer2 to port
>> >> > 1002.
>> >> >
>> >> > I then went to computer1 and manage to change the setting under
>> >> > advance to re-route all TCP 1002 service to computer2.
>> >> > When I go back to computer1 and type into the RDP-client
>> >> > computer2:1002 it works great.
>> >> >
>> >> > The problem is that when I get out of my local network lets say
>> >> > computer3 and try
>> >> > xxx.xxx.xxx: 1002 it does not work.
>> >> >
>> >> > Does anybody know what the problem is? Any help will be appreciated.
>> >> > In fact thanks for reading this far!
>> >> >
>> >> > al
>> >>
>> >
>> >
>>
>
>