Security server name resolution problem

[avarcher]

I've configured a security server and it works perfectly tested internally, when we test it from an external source we get a name resolution problem. We access it externally using , we get logged in OK and then we get the error ;-

'A connection to the VDM server https://securityservercomputername:443/ could not be established, The Server name could not be resolved'.

This is because <SecurityServerComputername> is, of course, not resolvable externally.

I've configured the Security Server with a C:\Program Files\VMware\VMware VDM\Server\sslgateway\conf\locked.properties file containing ;-

clientHost=x.y.z.a
clientPort=443
clientProtocol=https

... and rebooted it. The Event Viewer has an entry ...

The VDM Secure Gateway will be accessed using URL

.. so it seems the locked.properties file is not doing its job.

I've set the External URL on the Connection Server as http://x.y.z.a:443.

Or - I've missed something, any help welcome.

Cheers, Andy.

[mpryor · Accepted solution]

It doesn't look like you've missed something, but the log line "The VDM Secure Gateway will be accessed using URL https://securityservercomputername:443" obviously suggests otherwise, first off double check that you have case and spelling correct for the clientHost property in the file, it is case sensitive.

If you're certain that is correct, you can turn on full logging on the server (there's a Start menu shortcut for it in VDM 2.1). You should see one of the following log lines when starting up the service (logs at c:\documents and settings\all users\application data\vmware\vdm\logs):

DEBUG Loading locked properties.

or, if something is going wrong

DEBUG No locked properties applied. (locked.properties)

TRACE Locked property open returned: \[ERROR GOES HERE\]

[avarcher]

Hi, and thanks for this.

The only reference to locked in the logfile is ....

13:08:06,640 DEBUG <Thread-1> Loading local properties.

13:08:06,640 DEBUG <Thread-1> No locked properties applied. (locked.properties)

13:08:06,656 DEBUG <Thread-1> No HTML admin adaptor

In my original post everything, the path and filename and content is copied /pasted from the actual implementation.

Thanks, Andy.

[avarcher]

Sorry ...

13:17:08,656 DEBUG <Thread-1> No locked properties applied. (locked.properties)

13:17:08,656 TRACE <Thread-1> Locked property open returned: java.io.FileNotFoundException: locked.properties (The system cannot find the file specified) com.vmware.vdi.ice.server.Ice.a(SourceFile:479)

java.io.FileNotFoundException: locked.properties (The system cannot find the file specified)

at java.io.FileInputStream.open(Native Method)

at java.io.FileInputStream.<init>(Unknown Source)

at java.io.FileInputStream.<init>(Unknown Source)

at com.vmware.vdi.ice.server.Ice.a(SourceFile:470)

at com.vmware.vdi.ice.server.JMXServer.main(SourceFile:92)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at net.propero.workspace.windowsinfrastructure.tunnelservice.TunnelService.run(SourceFile:36)

at java.lang.Thread.run(Unknown Source)

[mpryor]

So VDM can't find/load locked.properties - did you turn logging to full? You should get a trace message with the reason why it can't be loaded.

99% of the time this is because it can't find the file, just a couple of sanity checks for this:

• locked.properties is on the security server and not the connection server

• hide known extensions is turned off, the file isn't really being called locked.properties.properties by accident

• double check the spelling of the filename

EDIT: Crossed posts again! It is that VDM can't find the file, the points above do apply.

[avarcher]

Thanks, resolved, odd char at end of the filename, must have been a copy / paste problem.

Thanks for your help, Andy.