Re: Can I use in NAT enviroment?
From: Andreas Marschall [MVP TAPI] (Andreas.Marschall_at_I-B-A-M.de)
Date: 04/20/04
- Next message: Hilla: "Re: When recieving TSPI_lineSetCallData I need to know"
- Previous message: Jimmy: "Can I use in NAT enviroment?"
- In reply to: Jimmy: "Can I use in NAT enviroment?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 20 Apr 2004 07:51:30 +0200
"Jimmy" <kdryu@ecstel.co.kr> schrieb im Newsbeitrag
news:%23VpWGppJEHA.3412@TK2MSFTNGP09.phx.gbl...
> Can I use tapi client in NAT environment?
> TAPI Server and Domain Server have public IP address(211.xxx.xxx.xxx), but
> agents have private IP address(192.xx.xx.xx),
> and there is NAT between agents and Servers.
> In this case, agent can domain login, but tapi have some problem, just one
> agent use tapi function.
> First agent can use tapi function, but if second agent try to use tapi
> function, at that time, both agents can not
> use tapi function, all line is disabled in agent.
> If all agent use same network address(211.xxx.xxx.xxx), then all agent can
> use tapi function.
> I can not understand why I can not use tapi in NAT. Ping or other network
> function such as file sharing can be used in NAT.
Jimmy,
Here is a set of tests for TAPI 2.1 RemoteSP.tsp that I've collection over the
time.
Maybe something applies to your problem.
In addition see Michael Dunn's TAPI Site - FAQ:
Tips for getting TAPI 2.1 Client/Server working
http://www.rainyjay.com/tapi/faq_clientserv.htm
----------
PING in both directions: from each client to server; from server to each
client
----------
Access to shared directories:
Test whether a client can access shared directory on the server.
Test whether a server can access shared directory on the client.
----------
ControlPanel-Server-InUse:
To test whether your client contacts the server, open server control panel
applet
in the server, and open the "In Use" dialog box. If your client access the
server
(lineInitialize) it will open 2 PIPEs called tapisrv per attached client.
The problem is that it does not properly log on to and retrieve the
telephony device configured by TCMAPP in the server.
Under closer inspection with a packet sniffer it seems that there is a
failure in the remote procedure call. Two pipes do get opened to
\PIPE\TAPSVR successfully. Then instead of many TCP and MSPRC packet
exchanges (in the case of a client that works) the server closes down the
pipes and that's the end of the transactions. The result is a very delayed
client app with no devices available form the server.
I saw this same scenario when trying to configure
Win95/Win98 clients to use a TAPI server (NT clients
worked fine).
The only solution we found, totally by accident, was
to make the TAPI server a PDC of it's own domain, and
have a trust relationship between this domain and the
real domain the users use.
----------
NETSTAT:
Right after a client's attempt to connect (lineIntialize)
run netstat in a command window.
Look for two sockets like the following on the client:
Proto Local Foreign State
TCP CLIENT:xxxx SERVER:nbsession ESTABLISHED
TCP CLIENT:251 SERVER:yyyy ESTABLISHED
And on the server:
Proto Local Foreign State
TCP SERVER:nbsession CLIENT:xxxx ESTABLISHED
TCP SERVER:yyyy CLIENT:251 ESTABLISHED
If you don't see the first connection, or it's not in the
established state, this means the client can't connect to the
server's net bios port (over which the RPC takes place).
Make sure the user has "Access this computer from network"
rights on the server.
The same goes for the second connection. Make sure the account
that TAPISRV runs under on the server has "Access this computer
from network" rights. You can check this on a NT client, I don't
think you can on a 95/98 client.
If you see the two sockets and still no line devices, then look
at tcmapp on the server.
If you are setting up 95 clients do everything in the readme/docs
that come with the tapi21 download, it is all necessary.
-- Best Regards Andreas Marschall Microsoft MVP for TAPI / Windows SDK TAPI / TSP Developer and Tester http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm * Please post all messages and replies to the newsgroup so all may * benefit from the discussion. Private mail is usually not replied to. * This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: Hilla: "Re: When recieving TSPI_lineSetCallData I need to know"
- Previous message: Jimmy: "Can I use in NAT enviroment?"
- In reply to: Jimmy: "Can I use in NAT enviroment?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
