Win CE connect only once from some location

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

our customer have Wi-Fi lan for their barcode scanners (Symbol) with Win CE
and they are connecting to the TS. Everything is OK, but only on one place
which is farther and is connected through bridge (Yagi) is problematic. If
user connect from there, it can connect only once and next connection is
droped by server. After deleting MSLicencing registry key on the client, he
can connect once but next connection is droped (to be able to connect, the
MSLicencing key can not exist). Connection from Win XP is OK from this
location. It is problem only for Win CE. The Win CE client can connect
correctly from other locations...

Have you some hints?

the server is Windows 2000 server with SP4...
 
There might be a black hole router between your client and the TS,
which blocks packets above a certain size. This prevents the transfer
of the permanent TS CAL to the client (on first connection, the
client gets a temporary license, on second connection, it gets a
permanent license).

If this is the problem, you have to change the MTU size. Check the
Terminal Services FAQ, there are 2 items about this under
"Connectivity"

http://www.microsoft.com/windowsserver2003/community/centers/terminal
/terminal_faq.asp
 
I sent your answer to customer. Answer is, that they tested ping to 5MB and
all is ok. Have you some other hint or issue, why the permanent license is
not assigned for the Win CE? What else can block the assignment? (I am not
expert in Wi-Fi etc. but can be the problem hidden in the bridge?)

Thanks for your help...
 
I really don't know.
There are a couple of Windows 2000 post-SP4 hotfixes som have to
do with thin clients and licenses, but since the client can
connect from another location, that doesn't feel right either. It
is *exactly* the same client that can connect from another place,
isn't it, not just a similar model? Because then you also could
try to update the firmware in the client.
It sounds like the bridge is in some way the problem, but I don't
know enough about those to be of further help.

I list the hotfixes here anyway, in case you want to investigate
this track:

825027 - Terminal Services Licensing Denies Your Connection to
Your Terminal Server from Your WBT Device
http://support.microsoft.com/?kbid=825027

827355 - Event ID 1004 is logged when a thin client tries to
obtain a Terminal Services license
http://support.microsoft.com/?kbid=827355

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
 
Back
Top