|
| |
[../../_private/disc1_ahdr.htm]
NetMeeting 2.1 thru MS Proxy 2.0
From: Wes
Date: 2/20/98
Time: 12:53:14 PM
Remote Name: 192.168.0.2
Comments
In order to allow NetMeeting 2.1 to receive incoming calls through MS Proxy 2.0 you
must configure the Proxy clients Winsock .DLL's to allocate several ports on the Proxy
server for the clients exclusive use. Once this is done the Proxy server will listen for
incoming NetMeeting calls on the clients behalf.
Scenario: #1 If you want to designate a specific Proxy client as a
'receiver' of NetMeeting calls then place the following entries in a file named WSPCFG.INI
in the NetMeeting directory (normally C:\Program Files\NetMeeting\) on that Proxy client
machine. Whenever NetMeeting is running the Proxy will accept incoming calls for that
client.
Scenario: #2 If you want any Proxy client to be a 'receiver' of
NetMeeting calls on a first-come-first-served basis then place the following entries in
the MSPCLNT.INI (normally C:/Msp/Clients/) on the Proxy server. Whenever NetMeeting is
running the Proxy will listen for incoming calls for the client that ran NetMeeting first.
In either scenario all NetMeeting clients will be able to place outgoing calls.
[conf]
ServerBindTcpPorts=389,522,1503,1720,1731
KillOldSession=1
Persistent=1
NameResolutionForLocalHost=E
Note: This will allow only one client to receive incoming calls. The Proxy can't
'listen' for incoming calls for more than one client at a time.
The following table describes the possible entries that can be placed in either the
WSPCFG.INI or the MSPCLNT.INI file for a Windows Sockets application.
| Entry |
Description |
| [appname] |
The name of the application to which this configuration applies. |
| Disable |
This setting disables the WinSock Proxy service for all WinSock Proxy client
applications when the value is set to 1. In the [Common Configuration] section of the
Mspclnt.ini file, this setting overrides any other settings. |
| NameResolution |
By default, resolution for all dot-convention names is redirected. Forces name
resolution to local (L) or redirected (R), as specified. LocalBindTcpPortsSpecifies a TCP
port, list, or range that is bound locally. |
| LocalBindUdpPorts |
Specifies a UDP port, list, or range that is bound locally. |
| RemoteBindTcpPorts |
Specifies a TCP port, list, or range that is bound remotely. |
| RemoteBindUdpPorts |
Specifies a UDP port, list, or range that is bound remotely. |
| ServerBindTcpPorts |
Specifies a TCP port, list, or range used by a server application, so an
accept operation on these ports is intended to serve clients both locally and on the
Internet. Requires that the port is available both on the client and the Proxy Server
computer. |
| ProxyBindIp |
Specifies an IP address or list that is used when binding with a corresponding port.
Used by multiple servers that use the same port and need to bind to different ports on the
Proxy Server computer. The syntax of the entry is: ProxyBindIp=[port] : [IP address],
[port] : [IP address]. The port numbers apply to both TCP and UDP ports. |
| KillOldSession |
When the value is set to 1, this entry can be used to specify that if Proxy
Server holds a session from an old instance of an application, that session is terminated
before the application is granted a new session. This option solves the problem of
restarting an application. For example, if an application crashed, or did not close the
socket on which it was listening, it could have taken up to 10 minutes until Proxy Server
discovered that the session for the application should have been terminated. At that time
you would not have been able to restart the application because the port on which it was
listening was already in use. |
| Persistent |
When the value is set to 1, this entry can be used to maintain a specific
server state on the Proxy Server if a service is stopped and restarted and if the server
is not responding. The client sends a keep-alive message to the server periodically during
an active session. If the server is not responding, the client tries to restore the state
of the bound and listening sockets upon server restart. |
| ForceProxy |
Used to force a specific Proxy Server computer for a specific Windows Sockets
application. The syntax of the entry is: ForceProxy=[tag] : [entry], where tag equals i
for an IP address, x for an IPX address, or n for a name. Entry is the address of the
name. If the n flag is used, the WinSock Proxy service works over IP only. |
| ForceCredentials |
Used when running a Windows NT service or server application as a WinSock Proxy client
application. When the value is set to 1, forces the use of alternate user authentication
credentials stored locally on the computer running the Windows NT service. The user
credentials are stored on the client computer using the Credtool.exe application that is
provided with Proxy Server. User credentials must reference a user account that can be
authenticated by Proxy Server, either local to Proxy Server or in a domain trusted by
Proxy Server. The user account is normally set not to expire; otherwise, user credentials
need to be renewed each time the account expires. |
| NameResolutionForLocalHost |
Used to specify how the "LocalHost" computer name is resolved. (The
"LocalHost" computer name is resolved by calling the Windows Sockets API
function gethostbyname() using the "LocalHost" string, an empty string, or a
NULL string pointer.) This entry aids Windows Sockets applications that rely on the IP
addresses that the local host computer resolves to. Such applications call
gethostbyname("LocalHost") to find their local IP address and send it to an
Internet server. When this option is set to L (the default), gethostbyname() returns the
IP addresses of the local host computer. When this option is set to P, gethostbyname()
returns the IP addresses of the Proxy Server computer. When this option is set to E,
gethostbyname() returns only the external IP addresses of the Proxy Server computer (those
IP addresses that are not in the LAT). |
A port can appear in only one of the entries, either as Local, Remote (redirected), or
Server (redirected). There is no provision for client applications that require
connections both on the internal network and on the Internet. For such applications,
connections for the internal network are directed through Proxy Server as well.
[../../_private/disc1_aftr.htm]
|
