Can't run iwgetwfobj from remote server

I am trying to run iwgetwfobj from a different server. When I run the clt with the -s option and specify the server name or ip address, the message comes back with:

Could not connect to bmcmws10 or
Could not connect to [ip address]

Has anyone run into this? Running on Windows 2000. TS version 5.5.2.

Edited by raoliver on 10/29/02 02:38 PM (server time).

Find more posts tagged with

Comments

Migrateduser

Hmmm. I can use the -s to run iwgetwfobj on a remote UNIX TS server, but I also get the connect failure for Windows TS servers.

Anyone else?

bw

Bob Walden [bob.walden@interwoven.com]
Interwoven Education Group
IM: Yahoo, MSN bob_walden

Adam Stoller

I don't have the environment in which to try this out right now, but I believe there has been a problem (for a long time) trying to use CLTs remotely on Windows machines (from or to).

However, you could probably use Interwoven's OpenAPI to create a program that would do what you wanted ...

--fish
(Interwoven, Curriculum Development)

Migrateduser

Here is what I was told by one of our experts:

In reply to:

They need typically to run *compatible* versions of TeamSite; the RPC interface changed significantly in 5.5.x from previous versions.

The user also must exist on both local & remote machines in order to properly authenticate, I think, that is, to create a session.

"Compatible", I believe, includes same OS (eg. Windows to Windows, Solaris to Solaris).

Brinko Kobrin
Interwoven Staff Engineer

raoliver

We are running Windows 5.5.2 sp1 to Windows 5.5.2 sp 1.

The machines are in different domains. I am logged in as local administrator on the machine I am running the iwgetwfobj command.

Do the machines have to be in the same domain? Can I control the domain/userid used to authenticate.

Migrateduser

I have not done this myself, but if I understand Brinko's reploy correctly, you should either use a domain user that exist in both machines' local administrators group or a local user that exist on both machine and have the exact same password.

Hope it helps.

Migrateduser

More information from the expert:

In reply to:

I'm guessing [the scenario raoliver described] won't work, cuz:

The local administrator user on one machine has a unique SID; the other machine won't recognize it as equivalent to it's own Administrator.

You'd have to be logged into one box as a user (presumably domain user) which is valid for login on the other box. Not being a Windows networking guru, I think that means they have to share a domain of sorts.

Brinko Kobrin
Interwoven Staff Engineer