App. unable to open network ports

[Scott Trowbridge]

Hello,

I'm running win 2000 with terminal services enabled. All of my users have
thin-clients, NOT COMPUTERS, and have been working nicely with little
problems. However, we just installed an application that allows the users
to connect to a device within our network (192.168.x.x). After login into
this device, using a gui web based interface, it has a button to click on
which opens several ports (1024, 1027 & 1034) to establish communications.
When anyone, except users that have administrative priv., tries to opening
the ports, the system is unable to do so and marks each port with an 'X'
indicating that it has failed.

I guess the question is what permissions do I need to set to allow other
users the ability to open port? Or is there something else we need to look
at?

Scott

 

[Guest]

Try using filemon & regmon from Sysinternals to determine which objects users need permission to

http://www.workthin.com/tsdown.ht

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Scott Trowbridge wrote: ----

Hello

I'm running win 2000 with terminal services enabled. All of my users hav
thin-clients, NOT COMPUTERS, and have been working nicely with littl
problems. However, we just installed an application that allows the user
to connect to a device within our network (192.168.x.x). After login int
this device, using a gui web based interface, it has a button to click o
which opens several ports (1024, 1027 & 1034) to establish communications
When anyone, except users that have administrative priv., tries to openin
the ports, the system is unable to do so and marks each port with an 'X
indicating that it has failed

I guess the question is what permissions do I need to set to allow othe
users the ability to open port? Or is there something else we need to loo
at

Scot

 

[Scott Trowbridge]

Patrick--

I tried both Filemon and Regmon and they both point to TCP/IP and Winsock
that could be the problem. But, like most tools I've tried, nothing poits
to a 'smoking gun'.

Scott

 

[Guest]

Contact the developer of the application

Sorry no easy solution. :

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Scott Trowbridge wrote: ----

Patrick-

I tried both Filemon and Regmon and they both point to TCP/IP and Winsoc
that could be the problem. But, like most tools I've tried, nothing poit
to a 'smoking gun'

Scot