|
|
|
date: Wed, 7 Jun 2006 19:47:16 -0700,
group: microsoft.public.windowsnt.terminalserver.connectivity
back
Re: Dropped Connection
Mm, strange. Have you checked the network cable?
Are all these clients on the same LAN?
Same firmware version on the clients?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
"bobc007" wrote on 09 jun 2006:
>
> Vera Noest [MVP] wrote:
>> And the other 6 thin clients have no problem at all?
> Yes, the other clients have been running great.
>> Is there anyting in the EventLog on the TS?
> Nothing shows up in the event lof on the TS or in the Eventlog
> on the licensing server.
>> Is your TS (not the LS) setup to use the Per User licensing
>> mode?
> Yes, I just checked it.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Bobc007" wrote on 08 jun 2006 in
>> microsoft.public.windowsnt.terminalserver.connectivity:
>>
>> > I have 7 Wyse S30 terminals installed and connecting to a
>> > single 2003 terminal server. One of the Wyse boxes had a
>> > problem dropping it's connection. Sometimes it would
>> > re-connect and other times I'd have to re-start the box. I
>> > traded out the problem unit for one of my other working boxes
>> > and found the problem seemed to follow the bad box around.
>> > Finally I sent the box back to Wyse and got it replaced. Had
>> > the same problem. I'm somewhat stumped about the problem. My
>> > licensing server is on another server and setup for per user
>> > licensing. Any idea's about how to solve this problem?
>> >
>> > Thanks, Bob
date: Fri, 09 Jun 2006 06:37:18 -0700
author: Vera Noest [MVP]
Re: Dropped Connection
My first thought from the beginning was a bad cable, but I've tested
the cable and have even used a laptop with this cable to hook to the TS
and not had any problem. All the clients are also on the same LAN and
all the WYse boxes have the same firmware version. I'm using RDP to
connect and they all run the same version. It seems like there must be
some setting on the TS because this is happening on the new replacement
box also, I'm just not sure where else to look.
Vera Noest [MVP] wrote:
> Mm, strange. Have you checked the network cable?
> Are all these clients on the same LAN?
> Same firmware version on the clients?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> "bobc007" wrote on 09 jun 2006:
>
> >
> > Vera Noest [MVP] wrote:
> >> And the other 6 thin clients have no problem at all?
> > Yes, the other clients have been running great.
> >> Is there anyting in the EventLog on the TS?
> > Nothing shows up in the event lof on the TS or in the Eventlog
> > on the licensing server.
> >> Is your TS (not the LS) setup to use the Per User licensing
> >> mode?
> > Yes, I just checked it.
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> "Bobc007" wrote on 08 jun 2006 in
> >> microsoft.public.windowsnt.terminalserver.connectivity:
> >>
> >> > I have 7 Wyse S30 terminals installed and connecting to a
> >> > single 2003 terminal server. One of the Wyse boxes had a
> >> > problem dropping it's connection. Sometimes it would
> >> > re-connect and other times I'd have to re-start the box. I
> >> > traded out the problem unit for one of my other working boxes
> >> > and found the problem seemed to follow the bad box around.
> >> > Finally I sent the box back to Wyse and got it replaced. Had
> >> > the same problem. I'm somewhat stumped about the problem. My
> >> > licensing server is on another server and setup for per user
> >> > licensing. Any idea's about how to solve this problem?
> >> >
> >> > Thanks, Bob
date: 10 Jun 2006 07:26:15 -0700
author: bobc007
Re: Dropped Connection
Yes, I'm also running out of ideas, nothing seems to fit your
problem. A misconfigured TS would affect all clients, so that seems
unlikely as well.
Are you running SP1 on the server?
I guess that I would enable verbose logging of the user
environment, to see if that gives you a clue, and probably also
capture and analyse the network traffic between the server and this
client.
221833 - How to enable user environment debug logging in retail
builds of Windows
http://support.microsoft.com/?kbid=221833
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"bobc007" wrote on 10 jun 2006 in
microsoft.public.windowsnt.terminalserver.connectivity:
> My first thought from the beginning was a bad cable, but I've
> tested the cable and have even used a laptop with this cable to
> hook to the TS and not had any problem. All the clients are
> also on the same LAN and all the WYse boxes have the same
> firmware version. I'm using RDP to connect and they all run the
> same version. It seems like there must be some setting on the
> TS because this is happening on the new replacement box also,
> I'm just not sure where else to look.
>
>
> Vera Noest [MVP] wrote:
>> Mm, strange. Have you checked the network cable?
>> Are all these clients on the same LAN?
>> Same firmware version on the clients?
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> "bobc007" wrote on 09 jun 2006:
>>
>> >
>> > Vera Noest [MVP] wrote:
>> >> And the other 6 thin clients have no problem at all?
>> > Yes, the other clients have been running great.
>> >> Is there anyting in the EventLog on the TS?
>> > Nothing shows up in the event lof on the TS or in the
>> > Eventlog on the licensing server.
>> >> Is your TS (not the LS) setup to use the Per User licensing
>> >> mode?
>> > Yes, I just checked it.
>> >>
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> "Bobc007" wrote on 08 jun 2006 in
>> >> microsoft.public.windowsnt.terminalserver.connectivity:
>> >>
>> >> > I have 7 Wyse S30 terminals installed and connecting to a
>> >> > single 2003 terminal server. One of the Wyse boxes had a
>> >> > problem dropping it's connection. Sometimes it would
>> >> > re-connect and other times I'd have to re-start the box.
>> >> > I traded out the problem unit for one of my other working
>> >> > boxes and found the problem seemed to follow the bad box
>> >> > around. Finally I sent the box back to Wyse and got it
>> >> > replaced. Had the same problem. I'm somewhat stumped
>> >> > about the problem. My licensing server is on another
>> >> > server and setup for per user licensing. Any idea's about
>> >> > how to solve this problem?
>> >> >
>> >> > Thanks, Bob
date: Sat, 10 Jun 2006 12:35:52 -0700
author: Vera Noest [MVP]
Re: Dropped Connection
I'm running SP1. I've gon ahead and setup the logging as you
suggested, so I'll see what that shows up. Thanks
Vera Noest [MVP] wrote:
> Yes, I'm also running out of ideas, nothing seems to fit your
> problem. A misconfigured TS would affect all clients, so that seems
> unlikely as well.
> Are you running SP1 on the server?
>
> I guess that I would enable verbose logging of the user
> environment, to see if that gives you a clue, and probably also
> capture and analyse the network traffic between the server and this
> client.
>
> 221833 - How to enable user environment debug logging in retail
> builds of Windows
> http://support.microsoft.com/?kbid=221833
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "bobc007" wrote on 10 jun 2006 in
> microsoft.public.windowsnt.terminalserver.connectivity:
>
> > My first thought from the beginning was a bad cable, but I've
> > tested the cable and have even used a laptop with this cable to
> > hook to the TS and not had any problem. All the clients are
> > also on the same LAN and all the WYse boxes have the same
> > firmware version. I'm using RDP to connect and they all run the
> > same version. It seems like there must be some setting on the
> > TS because this is happening on the new replacement box also,
> > I'm just not sure where else to look.
> >
> >
> > Vera Noest [MVP] wrote:
> >> Mm, strange. Have you checked the network cable?
> >> Are all these clients on the same LAN?
> >> Same firmware version on the clients?
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> *----------- Please reply in newsgroup -------------*
> >>
> >> "bobc007" wrote on 09 jun 2006:
> >>
> >> >
> >> > Vera Noest [MVP] wrote:
> >> >> And the other 6 thin clients have no problem at all?
> >> > Yes, the other clients have been running great.
> >> >> Is there anyting in the EventLog on the TS?
> >> > Nothing shows up in the event lof on the TS or in the
> >> > Eventlog on the licensing server.
> >> >> Is your TS (not the LS) setup to use the Per User licensing
> >> >> mode?
> >> > Yes, I just checked it.
> >> >>
> >> >> _________________________________________________________
> >> >> Vera Noest
> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> >> TS troubleshooting: http://ts.veranoest.net
> >> >> ___ please respond in newsgroup, NOT by private email ___
> >> >>
> >> >> "Bobc007" wrote on 08 jun 2006 in
> >> >> microsoft.public.windowsnt.terminalserver.connectivity:
> >> >>
> >> >> > I have 7 Wyse S30 terminals installed and connecting to a
> >> >> > single 2003 terminal server. One of the Wyse boxes had a
> >> >> > problem dropping it's connection. Sometimes it would
> >> >> > re-connect and other times I'd have to re-start the box.
> >> >> > I traded out the problem unit for one of my other working
> >> >> > boxes and found the problem seemed to follow the bad box
> >> >> > around. Finally I sent the box back to Wyse and got it
> >> >> > replaced. Had the same problem. I'm somewhat stumped
> >> >> > about the problem. My licensing server is on another
> >> >> > server and setup for per user licensing. Any idea's about
> >> >> > how to solve this problem?
> >> >> >
> >> >> > Thanks, Bob
date: 12 Jun 2006 13:12:07 -0700
author: bobc007
|
|
