The page cannot be displayed

[Jerry Sehlhorst]

Unable to get some managed systems to show their Systems Management Homepage. The web page displays the error "The page cannot be displayed". The page does work from the server itself. I have the certificate from the CIM and the settings set to trust the CIM. The management protocols are SNMP:1.0, SSH:SSH-2.0-OpenSSH_3.7.1p1, SMH:1. Any suggestions??

[Rob Buxton]

Some kind of DNS issue?

From the CMS Server can you browse directly to the Web Page of the Agent on the remote Server?
If not, try resolving the name, e.g. nslookup.

[Jerry Sehlhorst]

I don't believe it is DNS related because it does translate to IP. When I browse from the CIM it gives me the same error. I also tried using the Ip from IE and get the same error. It appears like it blocks external connections.

[Rob Buxton]

IM doesn't block any access that I know of.
But, if there's some filtering / firewall between the CMS and the Client Server it will not get access unless some ports are enabled. You need to let 2301 and 2381 get access from the CMS to the Client. You need these opened up from Client to CMS if you want full VCA functionality.

[Jerry Sehlhorst]

We are not blocking those ports. It works on some managed systems on the same LAN.

[Rob Buxton]

Hmmm... interesting.
When you try and browse directly to http://ServerX:2301 from the CMS Server and get Page not found but the same works directly from ServerX it does seem to indicate something is getting misdirected somewhere. This eliminates IM at this point as it's just browser technology.

I would still try nslookup on the names and compare results on good vs bad servers. I'd also look at entries in the bypass proxy list or similar Browser issues.

[Jerry Sehlhorst]

I was able to track down the specific issue. From the CIM server you can view the System page of the managed server. On this page it has General Information. It has IP, System Name, and DNS Name. Some managed systems have Fully quailied domain names listed under the DNS name. The systems that have the FQN do not work.
EX. https://serverx:2381 DOES WORK
but https://serverX.domain.com:2381 Does not work.
Also https://xxx.xxx.xxx.xxx:2381 Does not work.
Any way to change the DNS name?

[Jon Huber_1]

Jerry,
Not sure if you're working in one namespace or if you have several, but have you tried specifing the 'DNS suffix append list' under 'Advanced TCP/IP Settings', DNS tab for your SIM server?

IE, manually add:
yourdomain.com
subdomain.yourdomain.com
and any other domains in which your servers may be located. I have servers in multple domains and had to do this on the SIM server in order to rectify similar problems...
Otherwise you can play around with the "use this connections' DNS suffix in DNS registration' on your target servers to see if any luck...

[Rob Buxton · Accepted solution]

Just a guess, but this looks like a proxy issue.
In IE, do you have the Bypass Proxy for local addresses checked? If so, this would allow a request to https://server:2381 to bypass the proxy whereas those with the FQDN will not.

If so, you could add entries for the domain and IP addresses into the Bypass Proxy list.
e.g. *.yourdomain.com; 10.*

[Jerry Sehlhorst]

Thanks Rob. That was it. I had to add the addresses to the bypass proxy list.

[Rob Buxton]

And that check box for Bypass Proxy for Local Addresses is interesting in that it is not emulated in other Browsers. It just accepts any single name, whereas on other browsers you need to start adding the domain name to the exclusion list.

Alas, that doesn't work here as the internal and external FQDN's are the same. So I need to add individual server names to the exclusion list to get Mozilla to work.