My Oracle Support Banner

Adding Node Using DCOM In GlassFish Server 3.1.2 Fails With Errors (Doc ID 1465991.1)

Last updated on AUGUST 16, 2018

Applies to:

Oracle GlassFish Server - Version 3.1.2 and later
Microsoft Windows x64 (64-bit)
Microsoft Windows (32-bit)

Symptoms

Windows users now have the flexibility to administer Glassfish clusters and instances remotely using SSH or DCOM.  

After following the official documentation on setting up DCOM at http://docs.oracle.com/cd/E26576_01/doc.312/e24934/ssh-setup.htm#CEGIFJJF  the following message is received, even though the provided username and password are correct:

Successfully verified that the host, test01.example.com, is not the local machine as required. Successfully resolved host name to: test01.example.com/192.168.100.25. Successfully connected to DCOM Port at port 135 on host test01.example.com. Successfully connected to NetBIOS Session Service at port 139 on host test01.example.com. Successfully connected to Windows Shares at port 445 on host test01.example.com. The remote file, F:\ORACLE\AppServer doesn't exist on test01.example.com : Logon failure: unknown user name or bad password.

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.