I have a pair of new Intel Xserves which don't seem to want to play
nicely with Server Admin & Server Monitor when being accessed remotely.
Both Xserves are running OS X Server 10.4.10 with seemingly all Apple-
provided updates installed, including the Xserve firmware update.
Because there is a firewall between the Xserves and my MacBook Pro,
I've had to open up various ports to access management tools on the
Xserves. I've opened:
FYI, both Xserves have a public (en0) and private (en1) IP address. I
am not using LOM. When I try and configure Server Monitor on my
(10.4.10) MacBook Pro, the Intel Xserves simply never respond to the
client Server Monitor requests, regardless of whether or not I use
the public or private IP address. If I use ARD to connect to either
of the Xserves, they both show the same symptoms: they cannot monitor
themselves (or each other) using either their public or private IP
address. The only way they will monitor themselves is if I enter the
Server Monitor client IP address as being 127.0.0.1.
Has anyone seen this before? I find it curious that all of my PowerPC
Xserves, using the exact same firewall rules, function flawlessly and
it's only their Intel brethren that seem to be misbehaving. Neither
console.log nor system.log on either Intel Xserve show any causes for
concern, both are fresh 10.4.9 Server installs which went to 10.4.10
via Software Update. Everything else on the servers seems to behave
just fine.
Thoughts? It is worth noting that I see _no_ packets being dropped
nor ports being blocked at the firewall (a Cisco PIX 525) between me
& the Xserves. The same firewall (and ruleset) separates me from the
Intel Xserves and the PowerPC Xserves.
