Terminal Services and \etc\services

Posted: 05-21-2004, 05:24 PM
We are working with a daemon-like Win2K/XP application that uses
GetServByName() to get the TCP/IP port to listen on. We would like to
get it to work with windows terminal services such that if multiple
terminal sessions are opened, each could have an instance of this
application running (on the same target machine, of course). In order
to make this possible, each instance would have to listen on a
different port.

Now, since there is a single common services file located in
\WINDOWS\system32\drivers\etc, it makes it difficult to have each
instance resolve into different port numbers (the service name is not
configurable).

Is there some way to trick the application to pick up different port
numbers? For example, if it was possible to change the location of
the services file to a unique directory for each terminal services
user, it would solve the problem. Or, if it was somehow possible to
intercept the GetServByName call... You get the idea.

Any thoughts?

--Joe G.
Reply With Quote

Responses to "Terminal Services and \etc\services"

Joe G.
Guest
Posts: n/a
 
Re: Terminal Services and \etc\services
Posted: 05-24-2004, 02:47 PM
BUMP

Anyone?
Reply With Quote
Jeffrey Randow (MVP)
Guest
Posts: n/a
 
Re: Terminal Services and \etc\services
Posted: 05-25-2004, 03:49 AM
I think this is above the knowledge base of most of us in here... Try
posting in the terminal servie or scripting/winsdk groups...

Jeffrey Randow (Windows Networking & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

On 21 May 2004 09:24:00 -0700, alienreserve@yahoo.com (Joe G.) wrote:
>We are working with a daemon-like Win2K/XP application that uses
>GetServByName() to get the TCP/IP port to listen on. We would like to
>get it to work with windows terminal services such that if multiple
>terminal sessions are opened, each could have an instance of this
>application running (on the same target machine, of course). In order
>to make this possible, each instance would have to listen on a
>different port.
>
>Now, since there is a single common services file located in
>\WINDOWS\system32\drivers\etc, it makes it difficult to have each
>instance resolve into different port numbers (the service name is not
>configurable).
>
>Is there some way to trick the application to pick up different port
>numbers? For example, if it was possible to change the location of
>the services file to a unique directory for each terminal services
>user, it would solve the problem. Or, if it was somehow possible to
>intercept the GetServByName call... You get the idea.
>
>Any thoughts?
>
>--Joe G.
Reply With Quote
 
LinkBack Thread Tools Display Modes
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may 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 On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Terminal Services Asussertown Windows XP Work Remotely 16 03-23-2007 11:35 PM
Terminal Services stacey Windows XP Configuration & Management 5 01-22-2005 12:31 AM
tsweb vs. terminal services Chris Windows XP Work Remotely 1 11-08-2003 02:50 AM
Terminal services in XP Pro F1Com Windows XP Work Remotely 2 10-31-2003 03:27 AM
XP and Terminal Services mcarter Windows XP Network & Web 0 07-07-2003 11:13 PM


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90