PC Review


Reply
Thread Tools Rate Thread

App. unable to open network ports

 
 
Scott Trowbridge
Guest
Posts: n/a
 
      21st May 2004
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





 
Reply With Quote
 
 
 
 
=?Utf-8?B?UGF0cmljayBSb3VzZSBbTVZQXQ==?=
Guest
Posts: n/a
 
      21st May 2004
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






 
Reply With Quote
 
Scott Trowbridge
Guest
Posts: n/a
 
      21st May 2004
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]" <(E-Mail Removed)> wrote in message
news:4E5D03FD-2B7D-4A75-9C4A-(E-Mail Removed)...
> 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
>
>
>
>
>
>




 
Reply With Quote
 
=?Utf-8?B?UGF0cmljayBSb3VzZSBbTVZQXQ==?=
Guest
Posts: n/a
 
      21st May 2004
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


"Patrick Rouse [MVP]" <(E-Mail Removed)> wrote in messag
news:4E5D03FD-2B7D-4A75-9C4A-(E-Mail Removed)..
> Try using filemon & regmon from Sysinternals to determine which object

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 user

hav
> thin-clients, NOT COMPUTERS, and have been working nicely with littl
> problems. However, we just installed an application that allows th

user
> to connect to a device within our network (192.168.x.x). After logi

int
> this device, using a gui web based interface, it has a button t

click o
> which opens several ports (1024, 1027 & 1034) to establis

communications
> When anyone, except users that have administrative priv., tries t

openin
> the ports, the system is unable to do so and marks each port with a

'X
> indicating that it has failed
>> I guess the question is what permissions do I need to set to allo

othe
> users the ability to open port? Or is there something else we nee

to loo
> at
>> Scot
>>>>>>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Unable to Open Some Files on a Home Network tcirinci Windows Vista Networking 1 2nd May 2009 03:45 PM
How to shutdown open network ports? ESmith Microsoft C# .NET 3 22nd Sep 2006 10:28 AM
Unable to open Network Connections Joe Microsoft Windows 2000 2 9th Sep 2005 03:44 PM
Unable to open Properties for My Network Places Floyd Drennon Windows XP Customization 1 16th Jul 2004 01:53 PM
Application unable to open network ports Scott Trowbridge Microsoft Windows 2000 Terminal Server Clients 0 21st May 2004 03:29 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 11:01 AM.