Home Forums OS X Server and Client Discussion Questions and Answers Kerberos DS 2 Network Cards

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #362766
    steve
    Participant

    I have an xserve running 10.4.2 with 2 network cards one connected to my ISP the other to the internal network. The FQDN of the external network card resolves to mail.mycompany.com as setup by our ISP. The FQDN of the internal network card resolves to xserve.mycompany.com as set up by me. When I promote our server to a Directory Master the Kerberos Realm grabs the FQDN of our external networ card rather than the internal, is this correct as Kerberos does not work.I thought that for Kerberos to work the realm should match the FQDN of my internal network card?

    Should the correct setup for DNS show the FQDN of the internal card matching the FQDN of the external card?

    I have also found that when I go to create home Directorys they also have the FQDN of the external network card as part of the path. I assumed that for network homes to work correctly they should have the FQDN of the internal card in the path?

    Can anyone clarify this for me?

    #362768
    premiermac
    Participant

    You could disable the external interface, set everything up, and then re-activate it later.

    #362775
    steve
    Participant

    Yes I could do that but its not really the answer Im looking for I’m hoping that someone knows the correct method to follow and could document it here….

    #362841
    Anonymous
    Guest

    How lame these forums are not a single reply so no one use the xserve with 2 network cards…..

    #362855
    steve
    Participant

    I dont think there lame Smile I just thought that might prevoke a repsonce and it it did!

    #362856
    Anonymous
    Guest

    [QUOTE]Why not tell it what realm you want when creating the master? It gives you that option.[/QUOTE]

    – I did try this and then got the problem of Kerberos starting but not working. Which is why I was interested in what others have done to get around this problem. I thought the answer would be make the FQDN on the internal NIC the same as the Exsternal but that seems to make no difference….

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.

Comments are closed