remote desktop listening port and drive porting

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Hey folks,

I have two XP Pro SP2 machines behind a router, which are Remote
Desktop-enabled. One machine is on the default port 3389 while the other is
on 3390 and these ports are forwarded to the appropriate static IP in the
router's config. The machine on 3389 works just great with drive, printer,
and serial connection porting, but none of these RD abilities work with the
machine using 3390 as the listening port. I can only browse the remote
desktop and files; the client drives do not appear in the server's 'My
Computer'. Does drive porting not work when you change the listening port?

Thanks for any advice,

Dave

--
______________________________
Remove "yourclothes" to reply directly.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Is it possible you have group policies set to block these on that particular PC?

http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/pree_rem_uvnl.asp

--
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...

"David Shorthouse" <davidshorthouse@shawyourclothes.ca> wrote in message
news:kL90d.373752$gE.209484@pd7tw3no...
> Hey folks,
>
> I have two XP Pro SP2 machines behind a router, which are Remote Desktop-enabled. One machine
> is on the default port 3389 while the other is on 3390 and these ports are forwarded to the
> appropriate static IP in the router's config. The machine on 3389 works just great with drive,
> printer, and serial connection porting, but none of these RD abilities work with the machine using
> 3390 as the listening port. I can only browse the remote desktop and files; the client drives do
> not appear in the server's 'My Computer'. Does drive porting not work when you change the
> listening port?
>
> Thanks for any advice,
>
> Dave
>
> --
> ______________________________
> Remove "yourclothes" to reply directly.
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Al spoke my mind---all the capabilities use the same port--should be an all
or nothing situation. I assume you are testing using the same client
machine, so you need to be looking at the host at 3390.

"David Shorthouse" <davidshorthouse@shawyourclothes.ca> wrote in message
news:kL90d.373752$gE.209484@pd7tw3no...
> Hey folks,
>
> I have two XP Pro SP2 machines behind a router, which are Remote
> Desktop-enabled. One machine is on the default port 3389 while the other
> is on 3390 and these ports are forwarded to the appropriate static IP in
> the router's config. The machine on 3389 works just great with drive,
> printer, and serial connection porting, but none of these RD abilities
> work with the machine using 3390 as the listening port. I can only browse
> the remote desktop and files; the client drives do not appear in the
> server's 'My Computer'. Does drive porting not work when you change the
> listening port?
>
> Thanks for any advice,
>
> Dave
>
> --
> ______________________________
> Remove "yourclothes" to reply directly.
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Thanks for the help, but the group policies were not set to prevent drive,
LPT, or COM port redirection for the server machine whose listening port was
changed to 3390 from the default. Strange that you suggest it would be an
all-or-nothing situation because I can browse the server's desktop, file
structure, etc. just the client's drives to not appear on the remote desktop
although everything works just fine on another server using the default
port.

Any other ideas? What accounts are needed on the server's drive security to
permit drive redirection in case I may have missed something?

Specs:

Client & Server: Windows XP Pro SP2
Linksys WRT54G with latest firmware and ports forwarded to appropriate
machines with static IP assigned

--
______________________________
Remove "yourclothes" to reply directly.
"Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in message
news:OuxTdQ1lEHA.3632@TK2MSFTNGP09.phx.gbl...
> Al spoke my mind---all the capabilities use the same port--should be an
> all or nothing situation. I assume you are testing using the same client
> machine, so you need to be looking at the host at 3390.
>
> "David Shorthouse" <davidshorthouse@shawyourclothes.ca> wrote in message
> news:kL90d.373752$gE.209484@pd7tw3no...
>> Hey folks,
>>
>> I have two XP Pro SP2 machines behind a router, which are Remote
>> Desktop-enabled. One machine is on the default port 3389 while the other
>> is on 3390 and these ports are forwarded to the appropriate static IP in
>> the router's config. The machine on 3389 works just great with drive,
>> printer, and serial connection porting, but none of these RD abilities
>> work with the machine using 3390 as the listening port. I can only browse
>> the remote desktop and files; the client drives do not appear in the
>> server's 'My Computer'. Does drive porting not work when you change the
>> listening port?
>>
>> Thanks for any advice,
>>
>> Dave
>>
>> --
>> ______________________________
>> Remove "yourclothes" to reply directly.
>>
>
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Try also forwarding UDP 3390... It doesn't have to have the UDP part
forwarded, but Virtual Channels (which use UDP) are used for the
different redirections.

Jeffrey Randow (Windows Networking & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

On Fri, 10 Sep 2004 22:20:32 GMT, "David Shorthouse"
<davidshorthouse@shawyourclothes.ca> wrote:

>Thanks for the help, but the group policies were not set to prevent drive,
>LPT, or COM port redirection for the server machine whose listening port was
>changed to 3390 from the default. Strange that you suggest it would be an
>all-or-nothing situation because I can browse the server's desktop, file
>structure, etc. just the client's drives to not appear on the remote desktop
>although everything works just fine on another server using the default
>port.
>
>Any other ideas? What accounts are needed on the server's drive security to
>permit drive redirection in case I may have missed something?
>
>Specs:
>
>Client & Server: Windows XP Pro SP2
>Linksys WRT54G with latest firmware and ports forwarded to appropriate
>machines with static IP assigned

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Jeffrey's given a good suggestion--it should not be needed, but if present
it will get used, as I understand it.

There have been bugs which have killed redirection in the past. In one
case, certain antivirus applications running on a PRE-SP1 XP host had this
effect. If you removed the antivirus, redirection worked fine. I believe
I've heard of another instance since then, but its escaping me.

Can you eliminate most third-party drivers? Any proprietary VPN software
installed?

"David Shorthouse" <davidshorthouse@shawyourclothes.ca> wrote in message
news:QMp0d.365179$M95.24387@pd7tw1no...
> Thanks for the help, but the group policies were not set to prevent drive,
> LPT, or COM port redirection for the server machine whose listening port
> was changed to 3390 from the default. Strange that you suggest it would be
> an all-or-nothing situation because I can browse the server's desktop,
> file structure, etc. just the client's drives to not appear on the remote
> desktop although everything works just fine on another server using the
> default port.
>
> Any other ideas? What accounts are needed on the server's drive security
> to permit drive redirection in case I may have missed something?
>
> Specs:
>
> Client & Server: Windows XP Pro SP2
> Linksys WRT54G with latest firmware and ports forwarded to appropriate
> machines with static IP assigned
>
> --
> ______________________________
> Remove "yourclothes" to reply directly.
> "Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in message
> news:OuxTdQ1lEHA.3632@TK2MSFTNGP09.phx.gbl...
>> Al spoke my mind---all the capabilities use the same port--should be an
>> all or nothing situation. I assume you are testing using the same client
>> machine, so you need to be looking at the host at 3390.
>>
>> "David Shorthouse" <davidshorthouse@shawyourclothes.ca> wrote in message
>> news:kL90d.373752$gE.209484@pd7tw3no...
>>> Hey folks,
>>>
>>> I have two XP Pro SP2 machines behind a router, which are Remote
>>> Desktop-enabled. One machine is on the default port 3389 while the other
>>> is on 3390 and these ports are forwarded to the appropriate static IP in
>>> the router's config. The machine on 3389 works just great with drive,
>>> printer, and serial connection porting, but none of these RD abilities
>>> work with the machine using 3390 as the listening port. I can only
>>> browse the remote desktop and files; the client drives do not appear in
>>> the server's 'My Computer'. Does drive porting not work when you change
>>> the listening port?
>>>
>>> Thanks for any advice,
>>>
>>> Dave
>>>
>>> --
>>> ______________________________
>>> Remove "yourclothes" to reply directly.
>>>
>>
>>
>
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Well, now I feel a bit silly. I reverted to the default port and
adjusted settings in my router's config and the Windows SP2 firewall and I
continue to have the problem. So, the fact that I changed the port number
obviously had nothing to do with this problem of the client drives not
appearing in the server's RD.
I guess then I either have some bizarre TCP/IP stack issues or there is
a third party app causing the problem. How the heck do I now try to resolve
this? The other RD server in my network that successfully displays the
client drives while in RD mode, albeit with different hardware, has almost
the same applications installed with some exceptions. Those that might be of
importance in this situation are:

stunnel 4.05 (http://www.stunnel.org)
IIS 5.1 using port 1126
IntelliPoint 5.2 and IntelliType Pro 5.0
Motherboard Monitor 5.0

Anyone know if these or other applications will break the drive porting
ability in RD?

Dave

> Hey folks,
>
> I have two XP Pro SP2 machines behind a router, which are Remote
> Desktop-enabled. One machine is on the default port 3389 while the other
> is on 3390 and these ports are forwarded to the appropriate static IP in
> the router's config. The machine on 3389 works just great with drive,
> printer, and serial connection porting, but none of these RD abilities
> work with the machine using 3390 as the listening port. I can only browse
> the remote desktop and files; the client drives do not appear in the
> server's 'My Computer'. Does drive porting not work when you change the
> listening port?
>
> Thanks for any advice,
>
> Dave
>
> --
> ______________________________
> Remove "yourclothes" to reply directly.
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

STUNNEL might interact with RD (depending on how you are using it)...

Jeffrey Randow (Windows Networking & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

On Sat, 11 Sep 2004 19:20:37 GMT, "David Shorthouse"
<davidshorthouse@shawyourclothes.ca> wrote:

> Well, now I feel a bit silly. I reverted to the default port and
>adjusted settings in my router's config and the Windows SP2 firewall and I
>continue to have the problem. So, the fact that I changed the port number
>obviously had nothing to do with this problem of the client drives not
>appearing in the server's RD.
> I guess then I either have some bizarre TCP/IP stack issues or there is
>a third party app causing the problem. How the heck do I now try to resolve
>this? The other RD server in my network that successfully displays the
>client drives while in RD mode, albeit with different hardware, has almost
>the same applications installed with some exceptions. Those that might be of
>importance in this situation are:
>
>stunnel 4.05 (http://www.stunnel.org)
>IIS 5.1 using port 1126
>IntelliPoint 5.2 and IntelliType Pro 5.0
>Motherboard Monitor 5.0
>
>Anyone know if these or other applications will break the drive porting
>ability in RD?
>
>Dave
>
>> Hey folks,
>>
>> I have two XP Pro SP2 machines behind a router, which are Remote
>> Desktop-enabled. One machine is on the default port 3389 while the other
>> is on 3390 and these ports are forwarded to the appropriate static IP in
>> the router's config. The machine on 3389 works just great with drive,
>> printer, and serial connection porting, but none of these RD abilities
>> work with the machine using 3390 as the listening port. I can only browse
>> the remote desktop and files; the client drives do not appear in the
>> server's 'My Computer'. Does drive porting not work when you change the
>> listening port?
>>
>> Thanks for any advice,
>>
>> Dave
>>
>> --
>> ______________________________
>> Remove "yourclothes" to reply directly.
>>
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Jeffrey,

Thanks for helping on this. Unfortunately, it doesn't seem to be an
stunnel issue as I just disabled it and still get the same issue of the
client drives not appearing on the server system during a RD session.
Obviously something else going on here.

Dave

> STUNNEL might interact with RD (depending on how you are using it)...
>
> Jeffrey Randow (Windows Networking & Smart Display MVP)
> jeffreyr-support@remotenetworktechnology.com
>
> Please post all responses to the newsgroups for the benefit
> of all USENET users. Messages sent via email may or may not
> be answered depending on time availability....
>
> Remote Networking Technology Support Site -
> http://www.remotenetworktechnology.com
> Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
>
> On Sat, 11 Sep 2004 19:20:37 GMT, "David Shorthouse"
> <davidshorthouse@shawyourclothes.ca> wrote:
>
>> Well, now I feel a bit silly. I reverted to the default port and
>>adjusted settings in my router's config and the Windows SP2 firewall and I
>>continue to have the problem. So, the fact that I changed the port number
>>obviously had nothing to do with this problem of the client drives not
>>appearing in the server's RD.
>> I guess then I either have some bizarre TCP/IP stack issues or there
>> is
>>a third party app causing the problem. How the heck do I now try to
>>resolve
>>this? The other RD server in my network that successfully displays the
>>client drives while in RD mode, albeit with different hardware, has almost
>>the same applications installed with some exceptions. Those that might be
>>of
>>importance in this situation are:
>>
>>stunnel 4.05 (http://www.stunnel.org)
>>IIS 5.1 using port 1126
>>IntelliPoint 5.2 and IntelliType Pro 5.0
>>Motherboard Monitor 5.0
>>
>>Anyone know if these or other applications will break the drive porting
>>ability in RD?
>>
>>Dave
>>
>>> Hey folks,
>>>
>>> I have two XP Pro SP2 machines behind a router, which are Remote
>>> Desktop-enabled. One machine is on the default port 3389 while the other
>>> is on 3390 and these ports are forwarded to the appropriate static IP in
>>> the router's config. The machine on 3389 works just great with drive,
>>> printer, and serial connection porting, but none of these RD abilities
>>> work with the machine using 3390 as the listening port. I can only
>>> browse
>>> the remote desktop and files; the client drives do not appear in the
>>> server's 'My Computer'. Does drive porting not work when you change the
>>> listening port?
>>>
>>> Thanks for any advice,
>>>
>>> Dave
>>>
>>> --
>>> ______________________________
>>> Remove "yourclothes" to reply directly.
>>>
>>
>