Title: | X.500 Directory Services |
Notice: | Sprt: FORTY2::X500_SUPPORT, Kits: 216.*, try dir/titl=OFFICIAL |
Moderator: | FORTY2::PULLEN |
Created: | Tue Jan 30 1990 |
Last Modified: | Thu Jun 05 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1016 |
Total number of notes: | 4299 |
Hello, I have a customer who is asking a question about ISOTP. He has Infobroker V2.1 and is using WWW browser, Netscape to perform Lookups. He is noticing that IBX takes about 30 seconds before any action is performed by the TCP layer. His analysis comes from a sniffer that is looking at the line while the query is being performed. he is seeing ISOTP being used and subsequently times out, then TCP takes over about 30 seconds and 15 seconds later, the query is displayed. He wants to know what is this ISOTP layer and why is it being used. His transport is TCP. Any idea what he is talking about? Thanks in advance for your support. Randy csc/at
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
978.1 | a-101.tunnel.crl.dec.com::FORTY2::PALKA | Andrew Palka Altavista Directory | Wed Feb 26 1997 09:53 | 11 | |
At a guess ISOTP is the OSI transport layer. Possibly IBX is attempting to use a CLNS or CONS nsap to connect to the DSA (and failing). Check the presentation address in the dua.defaults file. Either remove or correct the CLNS nsap you find there. Alternatively, you may be able to set 'use clns error reports' in the transport template - I think this is covered by the X.500 documentation. Andrew |