Re: App. unable to open network ports

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Scott Trowbridge (scott_at_hsmc-ul.com)
Date: 05/21/04 

Date: Fri, 21 May 2004 13:49:23 -0400

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

"Patrick Rouse [MVP]" <anonymous@discussions.microsoft.com> wrote in message
news:4E5D03FD-2B7D-4A75-9C4A-F6C4FCE032BC@microsoft.com...
> Try using filemon & regmon from Sysinternals to determine which objects
users need permission to.
>
> http://www.workthin.com/tsdown.htm
>
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
>
> ----- Scott Trowbridge wrote: -----
>
> 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
>
>
>
>
>
>

Quantcast