OD Master on multiple IP addresses

[fleecy]

Is there a way to setup an OD Master to actively work with multiple IP addresses?

I’ve encountered a (Tiger) server which has been setup using a public IP address as its main network connection and a local 192.x address on its second NIC.

Currently, OD only works on the public IP; if I use another public IP, I can connect to its directory and work with Kerberos.

If I use a local IP address, however, I can connect to the server using Directory Access, but Kerberos doesn’t work, and clients can’t login using network accounts.

I guess i could reformat the whole server with a local IP as its main network connection, but that’s not gonna be fun.

Is there a good workaround to make this server’s Kerberos listen to clients using local IP addresses?

[luke]

I have exactly the reverse problem. I have an OD Master which is multihomed on two networks. That is, it has two interfaces with two IPs connected to two separate subnets. It publishes both of its IPs to clients so that they can apparently use either one to connect to it, but I only want it to publish one of them. Any ideas?

[pucky@theloucks.]

Hey Gang, here’s what I did

Server1 has 2 network adapters
Server2 has 2 network adapters

Server1 has primary DNS
Server2 has sencondary DNS

all four adapters are pointing to their local (internal ip address for DNS)

The Primary Server has an in-addr.arpa for both the external (internet routable IPs) and also has an in-addr.arpa for the internal lan.

External DNS (hosted on a totally different network) points to the Server 1 and Server 2 External IPs
and internal users are using the internal DNS servers that have forward and backward lookups working for both servers.

Both servers are working great and Kerberos is also working

[Author]

Posts