Using the Admin Console (non-java) through a SOCKS connection

[C_J_Hund]

Hi all,

Has anyone ever had to get their admin console working through a SOCKS server?  The IP address of our SOCKS server is in the master's bp.conf file, but still I'm unable to attach to the master using the admin console.  The user/password I'm using to log in DOES work when I attach through the java admin console.  Seems like there's probably a step I'm missing here.

Master server is at 6.5.2A. 

Sincere thanks,
C.J.

[CRZ]

In what way do things it not work?  Is an error reported, or does it look more like a hang?

Is the inbound connection to the master logged when you fire up the admin console, and if so, does it show as coming from the host/IP address you're expecting?

Do you have anything interesting in the nbconsole log on the server on which you're attempting to use the console?  (Did you enable that log?)

[C_J_Hund]

No, I didn't enable that log.  How would I do that?  (I'm going to google that as well).

Here's a snippet from the admin log for the logon attempt I just tried:
11:22:16.013 [26810] <2> TAO: TAO (26810|1) - Transport_Cache_Manager::fill_set_i, current_size = 0, cache_maximum = 1024
11:22:16.013 [26810] <2> TAO: (26810|1) PBXIOP_Connector::get_local_address, policy supplied local addr:141.177.14.180
11:22:16.013 [26810] <2> TAO: (26810|1) PBXIOP_Connector::get_local_address using local addr 141.177.14.180
11:22:16.013 [26810] <2> TAO: (26810|1) PBXIOP_Connector::make_connection, attempting local bind to 0
11:22:16.015 [26810] <2> TAO: TAO (26810|1) PBXIOP connection to peer <141.177.14.180:1556> on 260
11:22:16.015 [26810] <2> TAO: TAO (26810|1) - Transport_Cache_Manager::bind_i, 0xffdf9568 -> 0x9569e0 Transport[260]
11:22:16.017 [26810] <2> TAO: TAO (26810|1) - Synch_Invocation::invoke_i, timeout on recv is <59996>
11:22:16.018 [26810] <2> TAO: TAO (26810|1) Synch_Invocation::invoke_i, timeout after recv is <59994> status <1>
11:22:16.019 [26810] <2> TAO: TAO (26810|1) Timeout is <0>

That IP address is not in the bp.conf file.  I'm going to make that change and see where I end up.

Thanks!

[C_J_Hund]

A little more info that might shed some insight:

master(root) # bpnbat -login
Authentication Broker: root
Authentication port [0 is default]:
Authentication type (NIS, NISPLUS, WINDOWS, vx, unixpwd): unixpwd
Optional VxSS shared libraries not loaded.  If using NetBackup Access Control please check your VxSS installation.

Perhaps I have something here that's not installed?

[C_J_Hund]

I think I know what my question is now:

Where would I look to troubleshoot an inbound connection problem?  The admin log?  That seems like the most obvious place to start.

[CRZ]

vnetd
bpcd

"nbconsole" is one of the logs on a Windows client for the Windows admin console.  I may have misunderstood your earlier post.  To enable it, create the folder: <install_path>\VERITAS\NetBackup\logs\nbconsole (or run the mklogdir.bat script in the logs subdirectory to create EVERY possible folder)

[C_J_Hund]

Thanks!

One other thing that's interesting.  I'm attempting to log on through the admin console as root, not myself.  The root user is in the auth.conf (which I think it HAS to be, right?), but I'm not in the auth.conf.  What's interesting is that when the logon through the admin console fails, it seem to think I was attempting to logon as myself and NOT root, because the error message has my user ID in it. 

I'm sure it all has something to do with going through this SOCKS connection.

[C_J_Hund]

vnetd
bpcd

---------

Neither of these two logs is present on the master, unfortunately.