Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
1192 views

Questoion Regarding VPN and Authentication

I am trying to access my network via Cisco VPN then authenticating to the
network with the client but am getting the "tree or server cannot be
found" error message. I used to be able to do this before upgrading my
client to 4.91. It is obviously a setting that I am not noticing, can
anyone give me a clue?

Thanks in advance for your help.
Labels (2)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Questoion Regarding VPN and Authentication

cheryl.schmitz@nfld.k12.mn.us wrote:

> I am trying to access my network via Cisco VPN then authenticating to the
> network with the client but am getting the "tree or server cannot be
> found" error message. I used to be able to do this before upgrading my
> client to 4.91. It is obviously a setting that I am not noticing, can
> anyone give me a clue?


DA server configured previously that got overwritten perhaps?

--
-andy
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Questoion Regarding VPN and Authentication

On Wed, 03 Aug 2005 23:56:48 GMT, cheryl.schmitz@nfld.k12.mn.us wrote:

>I am trying to access my network via Cisco VPN then authenticating to the
>network with the client but am getting the "tree or server cannot be
>found" error message.


This can be very version dependant, and each change from Cisco and/or Novell
seems to work a little bit differently.

"tree or server not found" means that your client (Novell) is not finding a
Directory Agent (DA) to talk to. If you open a command line window and type
"slpinfo /d" you'll probably see what DAs you have configured, and that the
state is not "UP".

If you have your client configured to use DNS names, this can be problematic
because you can't resolve the DNS names until after the VPN comes up and gives
you IP connectivity. If you configure the client to use IP addresses for the
DAs, this problem can be bypassed.

When the client starts, it tries to find and contact the DAs. Some versions are
better than others at retrying this from time to time. Generally newer is better
here, but not always.

When the VPN is established, assuming you have a recent version from Cisco, it
should be alerting all other network clients that a change has happened. The
other network clients, like Novell's, are then supposed to re-init themselves
and go find out what they can talk to now. Not all Cisco VPN client versions do
this correctly, and not all Novell client versions respond correctly here.

It works here, I'm using 4.91 with the Cisco VPN client. I have my DAs
configured using IP addresses.


---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu

I'm tired of receiving rubbish in my mailbox, so the E-mail address is
munged to foil the junkmail bots. Humans will figure it out on their own.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.