Icegrid host names

in Help Center
Suppose I have 3 computers (assume DNS names PC1, PC2 and PC3), one running a registry and the other two running one node each. My question is: which properties should be supplied with these DNS names? Can I omit any explicit DNS usage in the properties below?
icegridregistry properties (PC1):
IceGrid.Registry.Client.Endpoints=default -h PC1 -p 4061
IceGrid.Registry.Server.Endpoints=default -h PC1
IceGrid.Registry.Internal.Endpoints=default -h PC1
icegridnode properties (PC2):
IceGrid.Node.Endpoints=default -h PC2
icegridnode properties (PC3):
IceGrid.Node.Endpoints=default -h PC3
icegridregistry properties (PC1):
IceGrid.Registry.Client.Endpoints=default -h PC1 -p 4061
IceGrid.Registry.Server.Endpoints=default -h PC1
IceGrid.Registry.Internal.Endpoints=default -h PC1
icegridnode properties (PC2):
IceGrid.Node.Endpoints=default -h PC2
icegridnode properties (PC3):
IceGrid.Node.Endpoints=default -h PC3
0
Comments
Each of your IceGrid nodes needs to connect to the IceGrid registry, which is achieved with:
in the node configuration.
Then, in IceGrid.Node.Endpoints, IceGrid.Registry.Server.Endpoints and IceGrid.Registry.Internal.Endpoints, you may or not specify "-h PCx" depending on your situation. No "-h" is equivalent to "-h *", and configures this object adapter to listen on all network interfaces.
If PC2 and PC3 have just one external network interface, then no -h or -h * should be fine. If PC2 or PC3 has multiple network interfaces, and you can only use a specific interface for Ice communications between these PCs, then use -h <name>, where <name> is a DNS name that designates the desired network interface.
See Object Adapter Endpoints - Ice 3.5 - ZeroC for more details.
Best regards,
Bernard
I can omit "-h" on PC2 and PC3, but not on PC1. On PC1 I get a SocketException (WSAEAFNOSUPPORT) when I omit the "-h PC1" in client, server or internal properties. This also happens when I start a node on PC1, so it's not registry specific.
All PC's have only 1 network card, next to some VMWare adapters. The only difference is that PC1 = XP 64bit and PC2,PC3 = Win7 64bit. I have Ice.IPv6=0 on all machines. In any case, since PC1 is the main PC, I can live with specifying its DNS name.
It's not clear to me why you get this exception. Can you copy paste the error message that shows the Ice::SocketException? You could also try to enable Ice.Trace.Network=2 on the registry on PC1, this should print some tracing that might show the problematic address.
Cheers,
Benoit.
Note that no version of Ice supports XP 64 bits. See ZeroC - Supported Platforms for Ice 3.5.1. This does not mean it does not work for sure - just that we didn't test and don't support this platform.
Best regards,
Bernard
I get the following trace:
With DNS name
I get the following trace:
This is the ipconfig output
Which Ice version do you use? Are you sure IPv6 is disabled in the registry configuration file? It looks like IPv6 is still enabled and Ice tries to use the IPv6 address (but it doesn't work, we don't support IPv6 on XP). The best would be to upgrade to a supported operating system.
Cheers,
Benoit.