Forum Replies Created

Viewing 15 posts - 1 through 15 (of 49 total)
  • Author
    Posts
  • in reply to: local admin unable to login on OSX 10.5.8 Xserve #377393
    guitar24t
    Participant

    Have you tried logging in as the root user?
    Good Luck,
    Robert

    in reply to: XServe G5 Problems #377392
    guitar24t
    Participant

    Have you tried resetting the pram?
    hold Command-Option-P-R on startup
    It never hurts when there are startup problems.
    Good Luck,
    Robert

    in reply to: Mount share of Mac OS X Server as SMB instead of AFP #377391
    guitar24t
    Participant

    You are incorrect in saying that the server shares connect using samba with “Connect As…”
    Try turning of samba and connecting with that method. You will still connect. Now disable AFP. You will have a Connection Failed message.
    See if this works (I just tried on mine, but maybe yours is different?)
    Good Luck,
    Robert

    in reply to: Leopard Server DNS #377033
    guitar24t
    Participant

    No problem, glad I could help.
    Robert

    in reply to: Mac OS X Server 10.4.11 #376977
    guitar24t
    Participant

    You should change the computer to the 192.168.1.x range and delete the airport base station reservation. Assign the server to a high address i.e. 192.168.1.200. Then, under the DHCP tab of the internet settings, make the starting address 192.168.1.2 (provided that your router is 192.168.1.1) and the ending address 192.168.1.199. There will most likely never be 198+ computers on this single lan and this will also leave space for 50+ static ip’s to be assigned above 199 with no fear of them being taken over.

    After you perform these changes, make sure that mac os x server can still access the internet.

    As for DNS configuration, I suggest removing the zone that you created and follow my guide from adding a Primary Zone (Master).
    Good Luck, Robert

    in reply to: Mac OS X Server 10.4.11 #376970
    guitar24t
    Participant

    Yes, that’s definitely a problem. If the computer is on the network with the airport and the airport is a dhcp server, then it must be in the same range.
    Good Luck, Robert

    in reply to: Mac OS X Server 10.4.11 #376967
    guitar24t
    Participant

    My guide can be found at [url]http://www.studiosoundandvision.com/OSXDNS/[/url]
    Good Luck,
    Robert

    in reply to: Remote Access #376946
    guitar24t
    Participant

    No problem, glad I could help!
    Robert

    in reply to: Remote Access #376943
    guitar24t
    Participant

    No they do not. On the router (if they are home users), you need only forward port 5900 to the client! 😀
    Then you may use their external ip to access their computer through screen sharing, but setup this way, you must use another mac to control the client. If you wish to enable normal vnc access, under screen sharing, there is a Computer Settings… button. You enable vnc and type in a vnc password to use.
    But no, you don’t need .mac, thank goodness!
    Hope this helps,
    Robert

    in reply to: Leopard Server DNS #376942
    guitar24t
    Participant

    After replicating your configuration, I have found the solution!!! 😀
    However, you won’t believe me until you try it.

    As a preliminary test, open system preferences > network and choose the gear-wheel icon in the bottom left and choose set service order. Drag ethernet 1 to the top and ethernet 2 right below it. Click ok then apply settings. Now verify that the server itself is able to access google.com.

    Now for the REAL problem…

    The problem was AGAIN the firewall, only this time BECAUSE it was off.
    [code]To fix your problem, turn the firewall on and try to access the internet from the clients[/code]

    To me this would sound like a far-fetched fix if I had not experienced this problem myself.

    If you notice any lags in services on the server, I’m sure the firewall will be the problem. I suggest using another computer, maybe running linux? 😀

    Really hope this will do it for you. If you still have problems, try the gateway setup assistant to configure the firewall for DHCP and NAT.

    Good luck once again,
    Robert

    in reply to: Leopard Server DNS #376938
    guitar24t
    Participant

    Just a thought I had…
    Try turning the firewall off on the server if it is running (Gateway Setup turns it on by default). The Mac Firewall has caused me so many problems 😡 I can’t even begin to explain.
    Good Luck,
    Robert

    in reply to: Leopard Server DNS #376937
    guitar24t
    Participant

    Not sure if this will help but…
    If you try to access the site from the same client computer every time, you might want to flush the dns cache.
    In addition to this, clear the history, cookies, and caches of Safari.
    To flush the dns cache, open terminal and type
    [code]dscacheutil -flushcache[/code]
    This has helped me many times when my dns was failing in a browser.

    Because the ip doesn’t work either, nslookup is probably using a cached record for google.
    Try nslookup google.com again after you flush the cache.

    Good Luck,
    Robert

    in reply to: Leopard Server DNS #376934
    guitar24t
    Participant

    I was able to access my server a bit sooner than I thought.
    In Server Admin:
    On the overview tab of the NAT service, there is a button in the bottom right corner of the screen that says gateway setup assistant. Click it to automate the setup of the gateway. This will overwrite your DHCP subsets, but it will not be that difficult to set them up again. When you get to the part that asks for the gateway WAN interface, make sure you select the interface with the internet connected. You can verify this using the network settings in system preferences – NOTE: these will not necessarily match eth0 (or en0) and eth1 (or en1) in order. Then when it asks which LAN interfaces to use, make sure you use the other ethernet that you did not use previously.
    Finish the wizard. Make sure that the DNS, DHCP, and NAT services now are all running.
    Switch to the DHCP service and click on the Subnets tab.
    There may or may not be a (few) subnet there already. If there are, delete them all; we will start from scratch.

    As a demo:
    Add a new subnet.
    For the subnet name (for example) type 192.168.1
    For the starting address, type 192.168.1.2
    For the ending address, type 192.168.1.199
    For the subnet mask, type 255.255.255.0
    For the network interface, make sure you are using the port that the clients are connected to by checking it with the network utility (not system preferences).
    For the router, type the address of the router that your server is connected to (from system preferences). (I’m not sure if this will work for you. You might have to enter the ip address of your server?? If it doesn’t work the first way, it can’t hurt to try :D)
    Under the DNS tab, type the ip address of your server. You can also enter any LDAP info and WINS info you need to, but that won’t have a bearing on the internet.

    You can substitute any ip address you wish for the demo as long as they follow a conventional scheme. If there is no way you can make it work with your ips, try the same ips as the demo here.

    Lastly, test the clients! Hopefully this will work. If not, I might be free sometime next week. I can setup a remote session with a vpn. If you wish to do this, contact me through my site [url]http://www.studiosoundandvision.com/[/url]
    I imagine you want this fixed soon with the school year starting 😯

    Good Luck,
    Robert

    in reply to: Leopard Server DNS #376929
    guitar24t
    Participant

    I would be happy to help. The best suggestion I can make right now is to setup the dns server to forward non-authoritative queries to OpenDNS (my favorite)
    208.67.222.222
    208.67.220.220
    just to make sure the forwarders work correctly; If you are on leopard server, the best thing to do would be to use the setup wizard under one of the services (dhcp or gateway or nat?).

    To test if the dns server is the problem, type in 74.125.157.147 on the server in a browser and see if it resolves to google. Then type 74.125.157.147 in a client browser and see if it does the same.

    I am away from high speed internet access right now and a connection to my server, but when I get home on Sunday, I will post a guide that should work if I can figure it out with my existing services. I don’t have a clean install to test it on right now (and I don’t want to mess up what I have 😀 ). (Just for the record, I use OpenSUSE with Webmin installed to provide dns, but I have gotten Mac to work (eventually)).

    I assume that you are using a setup with an internet router that connects to your server through a lan and that you need different dns servers for each area of your building.
    If you can have the same dns server provide answers to the whole building, you could have the router provide the ip of the one server to all of the clients in the building for dns and connect the iMacs directly to the router (not quite sure of your setup there).
    I will do my best to help and good luck,
    Robert

    in reply to: AFP Firewall Required Ports #376772
    guitar24t
    Participant

    I have a similar problem even when I set the firewall to allow all traffic. The same happens with VNC connections and print services. The only thing I’ve found that helps this is to disable the firewall. I have reinstalled multiple times and the firewall always causes problems. Do away with it and setup a standalone firewall (or linux (or none like me 😀 )).
    Sorry if there is a way around this and I am ignorant.
    Good Luck,
    Robert

Viewing 15 posts - 1 through 15 (of 49 total)