| 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 |
There seems to be a problem with remote CLNS binds. I installed T3.1 on UNIX V4.0B with the patch for UNIX V4.0A installed. The DSA was configured with just the CLNS address. Local binds were fine. Binds from a V3.0-ECO3 system failed with could not transmit data to DSA. Binds over RFC1006 work locally and remotely once it's configured. Binds from the T3.1 system to other DSAs work. Looks like a DSA-listening problem on the T3.1 system. Wook
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 971.1 | FORTY2::PULLEN | Julian Pullen | Thu Feb 13 1997 12:56 | 13 | |
Wook,
I havent tried X.500 T3.1 on UNIX V4.0b, but I did
get some problem when I started using CLNS. There are
normally two CLNS nsaps, but only one form works
unless you do some NCL configuration. Since I am not
a DECnet expert I just use the form that works as below
dxim> bind test to address "DSA"/"DSA"/"DSA"/NS+49002AAA000400CBAA21,CLNS
The form 4900CA08002B******* did not work
Julian
| |||||
| 971.2 | LAN Address not the issue | wookpc.ogo.dec.com::LEE | Thu Feb 13 1997 22:04 | 8 | |
I only has the phase IV compatible NSAP configured. My understanding is that the other form is a null ethernet LAN address that is supposed to work in the absense of any phase 5 routers. This was not an issue in my case. I don't know what caused the problem, but it seems I've worked around it for now. Since I have other things to test, I'll let this on go for now. Wook | |||||