Vista and Terminal Server 2003 SP2

I'm running a Terminal Server machine with 6 computers connecting to it
remotely with no issues. I've recently had a client buy a new computer with
Vista installed and he can not connect. He gets the warning window that is
generated from my server, but hen after he clicks OK on the message window,
it only partially draws the Server 2003 logon screen and he can go no
further. I'm running XP machines with RDP 6.0 on them so I don't think
that's the issue. Also if I bring his tower and place in on my Local
Network, it seems to connect just fine, however connecting from a remote
location yields the above error. I've been trying to solve this problem for
about 2 months now and haven't gotten anywhere at all. Any help would be
greatly appreciated.

You may try to modify the MTU. This troubleshooting may help.

Troubleshooting terminal server issuesTroubleshooting Remote Desktop
Connection. Black screen while connecting to TS. Cause: 1. MTU size may be
too high. 2. you may have a print driver problem. ...
www.chicagotech.net/troubleshootingts.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"Kevin Marshall" <Kevin Marshall@discussions.microsoft.com> wrote in message
news:E6615D42-6FC9-4273-ABC8-8A06DFECDB77@microsoft.com...
> I'm running a Terminal Server machine with 6 computers connecting to it
> remotely with no issues. I've recently had a client buy a new computer
> with
> Vista installed and he can not connect. He gets the warning window that
> is
> generated from my server, but hen after he clicks OK on the message
> window,
> it only partially draws the Server 2003 logon screen and he can go no
> further. I'm running XP machines with RDP 6.0 on them so I don't think
> that's the issue. Also if I bring his tower and place in on my Local
> Network, it seems to connect just fine, however connecting from a remote
> location yields the above error. I've been trying to solve this problem
> for
> about 2 months now and haven't gotten anywhere at all. Any help would be
> greatly appreciated.

BoB,

Thanks for the speedy reply, however adjusted and did not have any
effect on the client. As far as print drivers, I've removed them one at a
time and it didn't seem to help either. When connects it still partially
draws the logon/password screen and just hangs there. Only on this Vista
machine, so it's gotta be something unique with Vista.


"Robert L. (MS-MVP)" wrote:

> You may try to modify the MTU. This troubleshooting may help.
>
> Troubleshooting terminal server issuesTroubleshooting Remote Desktop
> Connection. Black screen while connecting to TS. Cause: 1. MTU size may be
> too high. 2. you may have a print driver problem. ...
> www.chicagotech.net/troubleshootingts.htm
>
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
>
>
> "Kevin Marshall" <Kevin Marshall@discussions.microsoft.com> wrote in message
> news:E6615D42-6FC9-4273-ABC8-8A06DFECDB77@microsoft.com...
> > I'm running a Terminal Server machine with 6 computers connecting to it
> > remotely with no issues. I've recently had a client buy a new computer
> > with
> > Vista installed and he can not connect. He gets the warning window that
> > is
> > generated from my server, but hen after he clicks OK on the message
> > window,
> > it only partially draws the Server 2003 logon screen and he can go no
> > further. I'm running XP machines with RDP 6.0 on them so I don't think
> > that's the issue. Also if I bring his tower and place in on my Local
> > Network, it seems to connect just fine, however connecting from a remote
> > location yields the above error. I've been trying to solve this problem
> > for
> > about 2 months now and haven't gotten anywhere at all. Any help would be
> > greatly appreciated.
>
>

One thing you may want to try is remove the IPv6 completely (not just
disable).

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com


"Kevin Marshall" <KevinMarshall@discussions.microsoft.com> wrote in message
news:828EB6B7-A1FE-4F36-BE77-FFCD6CD15916@microsoft.com...
> BoB,
>
> Thanks for the speedy reply, however adjusted and did not have any
> effect on the client. As far as print drivers, I've removed them one at a
> time and it didn't seem to help either. When connects it still partially
> draws the logon/password screen and just hangs there. Only on this Vista
> machine, so it's gotta be something unique with Vista.
>
>
> "Robert L. (MS-MVP)" wrote:
>
>> You may try to modify the MTU. This troubleshooting may help.
>>
>> Troubleshooting terminal server issuesTroubleshooting Remote Desktop
>> Connection. Black screen while connecting to TS. Cause: 1. MTU size may
>> be
>> too high. 2. you may have a print driver problem. ...
>> www.chicagotech.net/troubleshootingts.htm
>>
>>
>> --
>> Bob Lin, MS-MVP, MCSE & CNE
>> Networking, Internet, Routing, VPN Troubleshooting on
>> http://www.ChicagoTech.net
>> How to Setup Windows, Network, VPN & Remote Access on
>> http://www.HowToNetworking.com
>>
>>
>> "Kevin Marshall" <Kevin Marshall@discussions.microsoft.com> wrote in
>> message
>> news:E6615D42-6FC9-4273-ABC8-8A06DFECDB77@microsoft.com...
>> > I'm running a Terminal Server machine with 6 computers connecting to it
>> > remotely with no issues. I've recently had a client buy a new computer
>> > with
>> > Vista installed and he can not connect. He gets the warning window
>> > that
>> > is
>> > generated from my server, but hen after he clicks OK on the message
>> > window,
>> > it only partially draws the Server 2003 logon screen and he can go no
>> > further. I'm running XP machines with RDP 6.0 on them so I don't think
>> > that's the issue. Also if I bring his tower and place in on my Local
>> > Network, it seems to connect just fine, however connecting from a
>> > remote
>> > location yields the above error. I've been trying to solve this
>> > problem
>> > for
>> > about 2 months now and haven't gotten anywhere at all. Any help would
>> > be
>> > greatly appreciated.
>>
>>