Client on different domain can't log into dataserv...

JoshuaHouser · ‎Oct 19, 2011

Hi folks,

As I'm struggling to keep my Ilink 3.4 server alive, our company decides to move some client machines to a different domain, and now they can't access Intralink.

I believe the issue is related to Oracle, but not really sure. I use a fully qualified name on the client install for my dataserver. Is there anything else I'm missing?

TYIA

JimAugeri · ‎Oct 19, 2011

Is the server name resolving at the clients? You might need to add the
name and IP address into the HOSTS file on the clients. We needed to do
that with some of our locations because of how they were (or weren't)
resolving the Pro/I dataserver. I have clients in 4 different (all
within the company) domains all around the globe connecting to 3
different Pro/I servers here in the states without any issues.

--Jim Augeri

MCAD Tool Support - Engineering Quality and Tools (EQT)

Honeywell Aerospace

9201 San Mateo Blvd. (MS B-3)

Albuquerque, NM 87113

Phone - 505.828.5808

Fax - 505.828.5500

james.a.augeri@honeywell.com

"Never again will one generation of veterans abandon another."

Founding Principle of Vietnam Veterans of America

This e-mail message and any attachments are for the use of the intended
recipient(s) and may be controlled by U.S. export control laws. Any
unauthorized review, use, disclosure or distribution of this
communication in whole or in part without the express written consent of
Honeywell, or the U.S. Government as required, is prohibited. If you are
not the intended recipient(s), please contact the sender by reply e-mail
and destroy the original message and any copies of the message as well
as any attachment(s) to the original message.

JoshuaHouser · ‎Oct 20, 2011

Hi Folks,

I just wanted to give a quick update.

Two suggestions I hope to try soon are to upate the Hosts file on the client to include the Intralink server name and IP, and renaming the sqlnet.ora file in the Ilink client loadpoint.

JoshuaHouser · ‎Oct 21, 2011

Success!

Thankyou folks for all the tips!

The winning tip was renaming sqlnet.ora (Douglas was the first to mention this one...thanks!).

Apparently <intralink loadpoint=">\sqlnet.ora is not necessary to run Intralink. After renaming, everything worked fine.

I did verify that DNS names were resolving on host and server and both pinged each other. Fully-qualified names are used at both ends as well.

Thanks again for all the help and suggestions!!

Client on different domain can't log into dataserver

Client on different domain can't log into dataserver