T.R | Title | User | Personal Name | Date | Lines |
---|
2062.1 | Can you run other apps via PPP? | TAMARA::FLANAGAN | | Fri Mar 14 1997 09:34 | 10 |
| Hi Giovanni,
The first question is can they use TCP/IP (via PPP) in another application
such as telnet? I.e. can you establish a TCP/IP link via PPP and run
other applications such a telnet or a webbrowser?
If you can run other applications using PPP and not TeamLinks then
would you please post the cfcdebug.log file? Thanks.
/ Peter
|
2062.2 | DLL/EXE name conflict? | NETRIX::"[email protected]" | Bob St.Jean | Fri Mar 14 1997 12:15 | 9 |
| Hi,
The CONNECT.EXE might be the problem. TeamLinks has a CONNECT.DLL
which is located in the \Windows\System directory. Check to see
if the Cisco TCP/IP package also has a DLL or EXE named CONNECT.
Bob
[Posted by WWW Notes gateway]
|
2062.3 | thanks for now... i'll get the infos | MLNORO::MALACRIDA | | Mon Mar 17 1997 04:10 | 8 |
| rep .1 and .2
Ok, i'll get the log and check if connect.exe has something to do
with Teamlinks not beeing able to connect to the server.
Thanks,
giovanni
|
2062.4 | more infos on this subject | MLNORO::MALACRIDA | | Thu Mar 20 1997 04:14 | 39 |
|
I've got some more infos on this subject:
0) ping, telnet and other application works
1) the same Cisco stack when used over a LAN does allows Teamlinks
to connect to the server
2) Cisco software does use a CONNECT.EXE which is NOT located under
\windows\system
3) when CFCLOGOPTIONS is used (with CONNECT and TRACE options) the
resulting debug file is ... empty
The stack produced by X400MAIL is the following:
X400MAIL caused a general protection error
in module CONNECT.EXE in 0006:000026d2.
Registers:
EAX=43a76b0a CS=3717 EIP=000026d2 EFLGS=00000203
EBX=000020a6 SS=2cd7 ESP=00006ae0 EBP=00006ae2
ECX=00000000 DS=3e47 ESI=00001409 FS=0000
EDX=00003d5a ES=506f EDI=00006bad GS=0000
Byte at address CS:EIP:
8e d8 33 c0 8d 66 fe 1f 5d 4d cb 90 8c d8 90 45
stack image:
6bbf3e47 3d570217 00000000 00000000 6c1a0000 6b4c2cd7 6b0a2cd7 00002cd7
08280000 6ce43e47 31410001 4c49414d 00004346 00000000 00000000 00000000
Is unclear to me if this stack is from a Teamlink image or if it is
from the CONNECT.EXE image in Cisco software. By the way, the customer
is telling me that CONNECT.EXE is a sort of "interface" between the
application and the underlaying communication software.
Any help really appreciated.
giovanni
|
2062.5 | If Cisco has a CONNECT.EXE then would clash with the TL CONNECT.DLL. | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Thu Mar 20 1997 10:38 | 12 |
| Giovanni,
If this Cisco CONNECT.EXE is running when TL INFOMAN starts, then
Windows will not load the TL CONNECT.DLL. Windows will make TL
use the CONNECT.EXE that's already loaded, instead of the CONNECT.DLL
TL really needs. It would not work, because these 2 CONNECT files are
from different companies have different purposes. It's a name clash.
Perhaps the products cannot be used together.
Bob
|
2062.6 | could be ... but it works over a LAN | MLNORO::MALACRIDA | | Thu Mar 20 1997 11:48 | 19 |
| Bob,
your answer does make sense, but it doesn't explain the fact that
Teamlinks is able to connect to the server when, instead of the dial-up
connection, a LAN connection is used.
As far as I could understand from the customer, CONNECT.EXE from Cisco
is used in both cases (I'll double check it, but I'm quite sure of
that).
Anyway, from your last phrase, I take that if the problem is really
a name clash, there is no possible workaround.
Thanks,
giovanni
|
2062.7 | | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Thu Mar 20 1997 17:41 | 9 |
| It's possible that the Cisco CONNECT.EXE is only used during a
dialup connection. Or that it doesn't have to run all the time
in a LAN situation. I don't know. I'm only guessing.
Maybe the customer can get someone from Cisco to explain when/how
it's used and perhaps suggest a work-around.
Bob
|