Terminal Server Thin Client Issues

[CNYTech]

I have a customer with a Fujitsu TeamPad thin client device using a cisco access point.

After a server reboot the client will connect ok the first time to the server using Terminal Services.

Upon a disconnect, when the thin client is turned back on a network error occurs and the client is disconnected again.

<event error 50 shows up in the system log>
The RDP protocol component WD detected an error
in the protocol stream and has disconnected the client

After this error the client is able to reconnect, but it does not start it's original session, it creates a new one and leaves the original open.

Steps I have taken already,

reinstalled terminal server
reinstalled the latest service pack
removed and recreated the rdp-Tcp configuration

any help would be appreciated.

CNYTech

http://www.xpbbs.com

- A PC and Windows XP Support Forum

 

[stiles123]

How are IP addresses distributed to this thin client?

There's a good chance that the Thin client is picking up a fresh IP address upon reboot and connecting to the Terminal Server using this new address. This might be confusing the box which starts up a fresh session.

If you're using DHCP, why not try creating a DHCP reservation for the thin client

 

[CNYTech]

the thin client has a static IP. no dhcp involved throughout the entire network.

CNYTech

http://www.xpbbs.com

- A PC and Windows XP Support Forum

 

[hewissa]

The error message points to the WD or Wireless Device. Could it be that the problem lies with the Cisco Access Point? How is it configured to interact with our network.

Hewissa

MCSE, CCNA, CIW