Server with Persistent Problems... PLEASE ADVISE!

Discussion in 'Mac OS X Server, Xserve, and Networking' started by whyrichard, Jul 9, 2013.

  1. macrumors 68000

    Joined:
    Aug 15, 2002
    #1
    HELLO!

    I have hooked up the server at our new 3 person studio. In general, typically, it works just fine. 3 mac's accessing a Mac Mini Server OSX 10.6.8 through ethernet. I am having some problems however creep up again and again...

    These problems in general are:
    -File Permissions on server are inconsistent and changeable.

    -Conflicting IP address arise from time to time.


    How to diagnose??? PLEASE ADVICE BRILLIANT MAC PEEPS!

    Background:
    -3 macs running SL to ML, connected to the server via ethernet
    -Mac Mini running OSX server 10.6.8, recently updated with a sata connection to a g-drive raid 5 hd
    -airport time capsule for occasional wifi connections and time machine support for the server
    -verizon router for internet

    I connected everything together using a somewhat convoluted system... Perhaps the problem lies there:

    -The internet goes from the verizon router to the time capsule to the server
    -the three macs go to the extra ethernet ports in the back of the verizon router as well as the time capsule

    It all usually works... HOW DO I BEGIN DIAGNOSING MY PERSISTENT YET INCONSISTENT PROBLEMS WITH THIS WACKY SERVER SETUP?

    thanks so much,

    Richard
     
  2. macrumors 6502a

    Joined:
    Jul 13, 2011
    Location:
    Mississippi
    #2
    Make sure only one of your devices is handing out IPs via DHCP. Either the Server, router, or TC... Not all of them.

    I'd prefer the router but, either will work.
     
  3. macrumors demi-god

    mmomega

    Joined:
    Dec 30, 2009
    Location:
    DFW, TX
    #3
    as mwhities said, I would start with checking if you have DHCP enabled on your Server then turn it off on your Time Capsule or vice versa. You only need 1 device handling DHCP services on the network.

    You can also set static IP address on the hardwired Macs.
     
  4. macrumors newbie

    Joined:
    Jul 7, 2013
    #4
    Hi,

    I had the same problem. Mine was a result of the DNS Machine A record not being set up properly. See http://www.mountainlionserver.com/dns/. It's has been working great since the change was made.

    HTH
     

Share This Page