Jump to content

Problems getting weight Scale towork over TS in UPS WorldShip

Guest dazed_&_confused

By Guest dazed_&_confused
in Windows NT Server

 Share

Recommended Posts

Guest dazed_&_confused

Guest dazed_&_confused

Posted
Posted

Hi all,

 

New to the forum, any help would really be appreciated. I am attempting to

get a Toledo weight scale (PS-160 Flat Top) to work over terminal services. I

have set the TS Client to connect to the server (Windows Server 2003) and

connect serial ports. It appears to be mapping the COM port for the scale to

COM2 (same as the client) but it does not actually do this. The local

resource is blank and the status is blank. When I actually map the COM port

using this command: NET USE COM2: \\tsclient\COM2 /persistent:yes the port

maps successfully, but the status of the port is "Unavailable."

 

Has anyone ever gotten this to work? If so, how? Also, please let me knowi

if I am doing something wrong.

  • Replies 3
  • Created
  • Last Reply

Popular Days

Popular Days

Guest Vera Noest [MVP]

Guest Vera Noest [MVP]

Posted
Posted

Re: Problems getting weight Scale towork over TS in UPS WorldShip

 

Check if the info here helps:

 

How can I verify that my local COM ports are redirected?

http://ts.veranoest.net/ts_faq_client_resources.htm#verify_COM_port

s

 

Can you post the result of the "change port /query" command here?

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?ZGF6ZWRfJl9jb25mdXNlZA==?=

<dazed_&_confused@discussions.microsoft.com> wrote on 03 jun 2008

in microsoft.public.windows.terminal_services:

> Hi all,

>

> New to the forum, any help would really be appreciated. I am

> attempting to get a Toledo weight scale (PS-160 Flat Top) to

> work over terminal services. I have set the TS Client to connect

> to the server (Windows Server 2003) and connect serial ports. It

> appears to be mapping the COM port for the scale to COM2 (same

> as the client) but it does not actually do this. The local

> resource is blank and the status is blank. When I actually map

> the COM port using this command: NET USE COM2: \\tsclient\COM2

> /persistent:yes the port maps successfully, but the status of

> the port is "Unavailable."

>

> Has anyone ever gotten this to work? If so, how? Also, please

> let me knowi if I am doing something wrong.

Guest dazed_&_confused

Guest dazed_&_confused

Posted
Posted

Re: Problems getting weight Scale towork over TS in UPS WorldShip

 

Well, it is still not working. Here is the results of my change port /query

command:

 

PLEASE NOTE: The COM Port has changed from COM2 to COM3 since the original

post.

 

 

-----------------START QUERY----------------------------

 

AUX = \DosDevices\COM1

COM2 = \Device\Oxser0

COM3 = \Device\RdpDrPort\;COM3:3\tsclient\COM3

COM5 = \Device\RdpDrPort\;COM5:3\tsclient\COM5

COM6 = \Device\Oxser3

LPT1 = \Device\RdpDrPort\;LPT1:3\tsclient\LPT1

OXPCIMF#*PNP0506#0A030000#{4d36e978-e325-11ce-bfc1-08002be10318} =

\Device\00000

05a

OXPCIMF#*PNP0506#0A030000#{86e0d1e0-8089-11d0-9ce4-08003e301f73} =

\Device\00000

05a

OXPCIMF#*PNP0506#0A030001#{4d36e978-e325-11ce-bfc1-08002be10318} =

\Device\00000

05b

OXPCIMF#*PNP0506#0A030001#{86e0d1e0-8089-11d0-9ce4-08003e301f73} =

\Device\00000

05b

OXPCIMF#*PNP0506#0A030002#{4d36e978-e325-11ce-bfc1-08002be10318} =

\Device\00000

05c

OXPCIMF#*PNP0506#0A030002#{86e0d1e0-8089-11d0-9ce4-08003e301f73} =

\Device\00000

05c

OXPCIMF#*PNP0506#0A030003#{4d36e978-e325-11ce-bfc1-08002be10318} =

\Device\00000

05d

OXPCIMF#*PNP0506#0A030003#{86e0d1e0-8089-11d0-9ce4-08003e301f73} =

\Device\00000

05d

PRN = \DosDevices\LPT1

 

C:\Documents and Settings\timd.WGW-DOMAIN-01>

 

 

 

 

 

 

 

 

 

 

 

 

"Vera Noest [MVP]" wrote:

> Check if the info here helps:

>

> How can I verify that my local COM ports are redirected?

> http://ts.veranoest.net/ts_faq_client_resources.htm#verify_COM_port

> s

>

> Can you post the result of the "change port /query" command here?

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?ZGF6ZWRfJl9jb25mdXNlZA==?=

> <dazed_&_confused@discussions.microsoft.com> wrote on 03 jun 2008

> in microsoft.public.windows.terminal_services:

>

> > Hi all,

> >

> > New to the forum, any help would really be appreciated. I am

> > attempting to get a Toledo weight scale (PS-160 Flat Top) to

> > work over terminal services. I have set the TS Client to connect

> > to the server (Windows Server 2003) and connect serial ports. It

> > appears to be mapping the COM port for the scale to COM2 (same

> > as the client) but it does not actually do this. The local

> > resource is blank and the status is blank. When I actually map

> > the COM port using this command: NET USE COM2: \\tsclient\COM2

> > /persistent:yes the port maps successfully, but the status of

> > the port is "Unavailable."

> >

> > Has anyone ever gotten this to work? If so, how? Also, please

> > let me knowi if I am doing something wrong.

>

Guest Vera Noest [MVP]

Guest Vera Noest [MVP]

Posted
Posted

Re: Problems getting weight Scale towork over TS in UPS WorldShip

 

Well, your COM ports are redirected successfully, so you're not

doing anything wrong.

Your best bet is to contact the vendor of the scale to ask them if

their product is supported under TS.

 

Alternatively, can you connect the scale to an USB port?

If that's not possible, have you applied the hotfix from KB article

938645?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?ZGF6ZWRfJl9jb25mdXNlZA==?=

<dazedconfused@discussions.microsoft.com> wrote on 11 jun 2008 in

microsoft.public.windows.terminal_services:

> Well, it is still not working. Here is the results of my change

> port /query command:

>

> PLEASE NOTE: The COM Port has changed from COM2 to COM3 since

> the original post.

>

>

> -----------------START QUERY----------------------------

>

> AUX = \DosDevices\COM1

> COM2 = \Device\Oxser0

> COM3 = \Device\RdpDrPort\;COM3:3\tsclient\COM3

> COM5 = \Device\RdpDrPort\;COM5:3\tsclient\COM5

> COM6 = \Device\Oxser3

> LPT1 = \Device\RdpDrPort\;LPT1:3\tsclient\LPT1

> OXPCIMF#*PNP0506#0A030000#{4d36e978-e325-11ce-bfc1-08002be10318}

> = \Device\00000

> 05a

> OXPCIMF#*PNP0506#0A030000#{86e0d1e0-8089-11d0-9ce4-08003e301f73}

> = \Device\00000

> 05a

> OXPCIMF#*PNP0506#0A030001#{4d36e978-e325-11ce-bfc1-08002be10318}

> = \Device\00000

> 05b

> OXPCIMF#*PNP0506#0A030001#{86e0d1e0-8089-11d0-9ce4-08003e301f73}

> = \Device\00000

> 05b

> OXPCIMF#*PNP0506#0A030002#{4d36e978-e325-11ce-bfc1-08002be10318}

> = \Device\00000

> 05c

> OXPCIMF#*PNP0506#0A030002#{86e0d1e0-8089-11d0-9ce4-08003e301f73}

> = \Device\00000

> 05c

> OXPCIMF#*PNP0506#0A030003#{4d36e978-e325-11ce-bfc1-08002be10318}

> = \Device\00000

> 05d

> OXPCIMF#*PNP0506#0A030003#{86e0d1e0-8089-11d0-9ce4-08003e301f73}

> = \Device\00000

> 05d

> PRN = \DosDevices\LPT1

>

> C:\Documents and Settings\timd.WGW-DOMAIN-01>

>

>

>

>

>

>

>

>

>

>

>

>

> "Vera Noest [MVP]" wrote:

>

>> Check if the info here helps:

>>

>> How can I verify that my local COM ports are redirected?

>> http://ts.veranoest.net/ts_faq_client_resources.htm#verify_COM_p

>> ort s

>>

>> Can you post the result of the "change port /query" command

>> here? _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> =?Utf-8?B?ZGF6ZWRfJl9jb25mdXNlZA==?=

>> <dazed_&_confused@discussions.microsoft.com> wrote on 03 jun

>> 2008 in microsoft.public.windows.terminal_services:

>>

>> > Hi all,

>> >

>> > New to the forum, any help would really be appreciated. I am

>> > attempting to get a Toledo weight scale (PS-160 Flat Top) to

>> > work over terminal services. I have set the TS Client to

>> > connect to the server (Windows Server 2003) and connect

>> > serial ports. It appears to be mapping the COM port for the

>> > scale to COM2 (same as the client) but it does not actually

>> > do this. The local resource is blank and the status is blank.

>> > When I actually map the COM port using this command: NET USE

>> > COM2: \\tsclient\COM2 /persistent:yes the port maps

>> > successfully, but the status of the port is "Unavailable."

>> >

>> > Has anyone ever gotten this to work? If so, how? Also, please

>> > let me knowi if I am doing something wrong.

 Share
Go to topic listing
×
×
  • Create New...