Snow Leopard Server dhcp assigns IP to clients, but sometimes that IP is blocked from reaching network

I have a problem that is driving me batty.
I have a Mac Mini Server acting as a gateway to the Internet. The cable modem is connected to the built in Ethernet, and the local net is configured with a USB Ethernet. I am running  DHCP on the local network, and all of the clients get IP's from the server with no problem. Sometimes an random IP appears to get blocked from accessing the network (can get the file servers on the local net, and cannot reach the Internet.) We can manually assign a different IP, and it might start working, but it might not. We just keep picking until we find one that works. Rebooting the server will fix the problem as well.
I see no indication of a problem in any of the logs on the server.
This setup has worked with no problem in the past, but I must have done something to the configuration as some point.
Any help will be appreciated!
Mark.

The proper way to set up your system is to set up the server's DNS as your primary DNS, entering into it all of your local devices and support, and use your ISP's DNS as forwarding DNS's. For help in doing this follow Mr. Hoffman's instructions.
Use your ISP's modem in bridge mode to provide you with a static IP. Use the server's DHCP system to provide all internal addresses, otherwise you won't have dynamically updated DNS information at the server level.
User your airport extreme as an AP. Set it up to use an internal static address as it's WAN address and shut down it's DHCP server allowing anything connected to it to receive it's IP address from the server. If you can't do that, then set up the Airport to provide DHCP with a reduced subset of addresses for only wireless devices. Let the server's DHCP provide all wire-based equipment addresses.
Turn off the wireless on the mac mini server and run wired from your ISP's modem. Before you do, however, you need to enter a static address into the TCP/IP section, including mask and gateway. This will avoid VPN and other service issues caused by having it turned on and receiving a DHCP address (at server can not, by nature, be a DHCP device).
To do remote desktop from the internet, you would connect through the WAN address provided to the server by your ISP, but you will need to open the firewall ports on the server. If you have the money, and want to most protection, you should invest in a firewall box like a SonicWall and insert this between your modem and the rest of your system. The SonicWall will provide faster, tighter attack protection and allows you to tie external service access down as tight as you want.
Hope this helps.

Similar Messages

  • Snow Leopard Client Dock Behavior & Binding to Snow Leopard Server

    Hi,
    I am at a loss on this issue. I am running a test server and client. I had bound my client to the server and was having difficulties with the dock settings on the client. I assumed it was a managed preferences issue on the server, so I checked all the ones I knew to check. It didn't appear that my client dock was being managed by my server. The problem was that the dock would switch from auto-hide to fixed and the preferences under dock could not be altered on the client.
    I've found that the only way to resolve this problem is to unbind the client from the server. Can anyone tell me what I need to be looking for within the server? Could there be an inherited preference from somewhere within the server?
    The other element to this is that this issue didn't arise until after I upgraded to 10.6.3. Prior the upgrade I was bound to the server, and the dock was fine. After the upgrade the dock preferences on the client were no longer able to be managed.
    I am new to server and need some help.
    Thanks

    Thanks!
    So, when I click Join..., type in the server, and then click on the Set Up Services button, I enter the username and password for the account I created on Snow Leopard Server. It switches the sheet to show that it's "Joining the server", and then fails with: "kGotAuthenticationFailure". The Password Service Server Log shows that is actually succeeded: "AUTH2: {0x4b5897f87cada0f20000001500000015, diana} DIGEST-MD5 authentication succeeded".
    If I actually enter an incorrect password, it right away gives me an "Authentication failed" message right below the password dialog in red.
    The console on the Snow Leopard client shows:
    10-01-21 11:10:16 AM System Preferences[248] -[ODCOSXServerJoinController(XSServiceDiscoveryProtocol) gotServicesInfo:fromServer:error:]: got error kGotAuthenticationFailure
    I don't see any other messages on the server that might explain this. Any ideas?
    This server was upgraded from Leopard Server, if that matters...

  • Upgrade From Snow Leopard Desktop to Snow Leopard Server

    I just installed Snow Leopard on my Mac Pro and it's running great! I upgraded it from 10.5 and it worked just fine for me. I was looking at the Snow Leopard Server and all the features it offers for the other Macs on my home network. My question is this: Can I install Snow Leopard Server on my Mac Pro without having to do a clean install? I have everything set up perfectly and I really don't want to have to reconfigure everything.
    My other question is, besides the server software, is there any difference between the server and desktop versions? More specifically, am I still going to be able to use my audio creation/editing software and play the few games I have? Does the server strip out any functionality or is it exactly the same thing as the desktop version, but with added server tools?
    Thanks in advance for your input!

    1. No, you cannot upgrade from Client to Server. You will need to erase and install.
    2. Generally, you can do the same things. It isn't exactly the same, even ignoring the server tools. Are there some things that won't work? Maybe. Namely because developers don't typically code with MOSXS in mind.
    My question to you is this: What do you want from MOSXS that you cannot do with the Mac OS Client? And are you set on using it on your Mac Pro?
    I ask because:
    1. Client does most of the thing people want to do that are "server" like.
    2. It isn't a good idea to mix server and production environments. OS X Server is typically easy to setup for basic operation, however, there will be issues and you will have to dig a little to get things working. Which means you will stopping and starting services, issuing terminal commands, modifying plists and .confs and rebooting. Sometimes it goes so wrong that you have to reinstall.
    This is why if you are serious about a server, you should really consider a separate machine. The Mac Mini is a great option for a light duty server.
    Also, carefully consider your needs. Can the things you want to do be accomplished with OS X Client and maybe a few web services. Not trying to sway you either way, but it isn't always as simple as "Click the Start button and the service is working."

  • Snow leopard server printing

    I've got a Mac mini running Snow Leopard Server (10.6.8) and the printer sharing has never worked. I have a Canon i860 printer hooked up to the Mac mini via USB. I have created an LPR print queue for that printer in the Server Admin app and everything seems fine -- it says that the printer service is running, it has a name, and it is showing up in the list of Bonjour printers from the other machines on the network.
    However, after adding this printer, no machines will print to that print queue over the network. The Mac mini will print to that printer over the direct USB connection, but other computers will not. Thus far:
    - the print queue shows up in the Bonjour list
    - you can add that printer to any computer on the network
    - you can (attempt) to print to it
    - but then all you get is an error message: "Network host 'Beefeater.local.' is busy; will retry in 30 seconds..."
    It is as though the print jobs are not sent because no jobs show up in the queue in the Server Admin app on the server.
    Any ideas?

    Found this thread: https://discussions.apple.com/message/13132912#13132912
    ...and renamed my print queue from "i860 on Beefeater" to "i860_beefeater"
    Now instead of getting the "will retry" message cited above, the problem is that it displays a message that says "Copying print data..." and then shows a message that says "Printer paused." Clicking "Resume" in the toolbar does nothing; no jobs show in the Snow Leopard Server print queue; and there is no indication that the printer itself is having any trouble.
    Ideas?

  • RSS feed from Snow Leopard server

    I want to host an RSS feed from my server. What settings would be necessary to accomplish this?

    The first things to do would be to download a program that will maintain your RSS feed.  Podcast spitter from the app store was the top hit when I did a search.  I've not used it, but it appears that it'll do the trick.
    Next, just create a website using the web service in Snow Leopard Server.
    Point Podcast Spitter at the share that hosts your web site and that should do the trick.
    When you upload your RSS feed, all the stuff needed to make it an RSS feed should go with it.
    Granted it's a VERY thinned out version of the steps needed to take, but the concepts are correct.
    If you need a more detailed description, write back with more info about how your server is set up and how it's connected to the internet.
    HTH
    -Graham

  • Tiger PPC clients with Snow Leopard Server

    I installed Snow Leopard Server (10.6.4) on an XServe.
    DNS - AFS - DHCP are set up correctly and have been checked several times.
    Clients have an AFP automount for network home directory. This share point is set up correctly as well and has been checked by Server's gurus.
    Everything is fine for Leopard clients but when it comes to connect to the Server with Tiger clients (PPC 10.4.11) something strange happens :
    - the first connection is correct and the home directory mounts normally
    - when the user disconnects and tries to connect a second time the folder home directory is not mounted and therefore the user can't have access to his/her home
    - although it's possible to mount the folder home directory using the "Connect to server…" command and then choose the user's home directory folder this isn't very handy with young students
    I have done extensive researches on Apple's documentation and on the forums but nobody seems to mention such a problem.
    Any idea what's wrong ? Already encountered the same issue ?
    Any help would be appreciate

    We have reported an automount bug which "may" be related to your problem to Apple. Our symptoms occurred in Leopard 10.5.8 and also in Snow Leopard 10.6.2 and resulted in user's seeing a message "You are unable to log in to the user account <account> at this time." This was due to an apparent problem in Mac OS X when reusing a share via automount.
    In our case we found that the period of time during which login is denied can be reduced by editing the file /etc/autofs.conf on the Mac and reducing the value of AUTOMOUNT_TIMEOUT.
    Hope this helps.

  • How do I upgrade Snow Leopard Server to Mountain Lion (client)?

    I have a Mac Mini Server edition (2010) with Snow Leopard Server (10.6.8) pre-installed. I don't like the interface of Server edition because 1) I don't need the server functions and 2) I prefer client OS's easier (less powerful I know) interface to do sharing, logging in, configuring.... etc.
    (I know I should've bought the non-server version with a DVD drive but I can't take it back now.)
    My question is, what's the easiest way of changing it to a 'client OS', preferably to the latest Mountain Lion? From forum posts it seems downgrading from 'server' to 'client' will definitely require a fresh install.  That's fine. I can move all my personal files to the second HDD in the Mini and do a fresh install of OS on the first HDD.
    I can see 'Mountain Lion' upgrade in the App Store, but it doesn't say if it's server or client. I am assuming it's a server upgrade?? What will happen if I purchase it for £13.99 in App Store? Or is there an alternative way?
    I have a USB Apple optical drive. I have a USB thumbdrive too for storing the OS image if required. Thank you. Any tips will be appreciated.

    Not_So wrote:
    I went to the AppStore and as I was running Snow Leopard Server it prompted me to purchase Lion Server which I didn't want.
    Luckily, I wasn't asked to purchase the 'Server' when I upgraded from SLS to Mountain Lion via the AppStore. I think your particular problem was mentioned in some other posts where the upgrade path to Lion became an infinite loop (hmmm... ). But that's all in the past now. Glad it all worked.

  • Windows 7 (Client) map a network drive VPN Snow Leopard Server

    Hi,
    I have a Mac Mini Snow Leopard Server and are using a VPN service.
    My services on the mac os x sls server are: AFP, DNS, Firewall, Open Directory, SMB and VPN.
    I can connect the VPN from Mac clients and Windows 7 clients, but I can only map a network drive/share point on Mac´s.
    On Windows 7 I get an error: path or name not found ( I am sure using the correct path, same from Mac client that works).
    When I am using my internal network LAN I can map a network drive using Windows 7 and Mac but outside over a VPN not (only Mac works).
    The only service, at this moment,  that I need is File Sharing outside my network LAN using a VPN.
    How can I map a network drive from a Windows 7 client using a VPN, is there any Firewall rules / SMB rules / File Sharing rules that I missed on the server side?
    Thank You.

    I really don't know what are going wrong with my settings. As you said/write it must be an easy setup.
    I'm using a Time Capsule and used the Server app to add VPN to the port forwarding also.
    When I am connected thru the VPN I tried to ping the Server IP and got no answer from it, from W7 client!?
    My Mac's are just working fine with AFP and SMB share points thru the VPN.
    I think I have missed some settings from the SMB or Firewall services for VPN with W7 client's or it is a Windows issue.....

  • Lion Clients 10.7.4 show network accounts are unavailable and server is not responding when binding to Snow Leopard server 10.6.8

    Hello,
    I am running Snow Leopard Server 10.6.8 and my clients are Lion 10.7.4.  While testing I had no issues binding 10.7.4 to our 10.6.8 server's OD.  I created a 10.7.4 image to push to all of our machines and in the beginning of last week I was able to push the image and get the machines to bind with OD and apply preferences on these machines through workgroup manager.  Towards the end of the week though this stopped working.  Now any time I bind a 10.7.4 client to OD it allows me to perform an authenticated bind and the machine shows up in workgroup manager but immediatley after binding the client the status jelly next to the OD server in the directory list is red and says "This server is not responding".  If I reboot the client I get a notification that "Network accounts are unavailable" at the login screen.  My preferences from workgroup manager are also not applying, which is my main concern because without workgroup manager my mac server is somewhat pointless as we use it for very little else. 
    I've since tried to bind a snow leopard machine (10.6.8) and this still is working with a green status jelly.  I've also built a lion machine from scratch, updated to the 10.7.4 combined update and am still getting the same issue where it shows the server is not responding when binding to OD.  I then applied the subsiquent OS update after the 10.7.4 combined update but the problem still persists.
    Is anyone else having this issue?  Any help would help me keep my sanity.
    Thanks,
    Dane

    Have you had any luck finding a solution to this?  The only thing I have found was to unbind and then bind without authentication.  Any help with progress on your end would be appreciated!
    Nick.

  • Are there any problems with Snow Leopard Server (Xserve) and PPC Clients

    Hi,
    are there any problems identified yet with Snow Leopard Server, installed on a Xserve and PPC Clients running Mac OS X Tiger and Leopard?
    Currently I have a Xserve Intel running Leopard Server and about 12 Mac Minis PPC running Mac OS X Tiger and Mac OS X Leopard. The Xserve serves services like DNS, OpenDirectory, Software Update Server, NetBoot, etc. All users have Home Directories stored on the Xserve.
    Now I want to install Snow Leoaprd Server on the Xserve, but I wonder if there are any problems using the PPC Clients? I have read something like this on a german website.
    Thanks!

    We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

  • Windows VNC clients cannot connect to Snow Leopard Server native VNC server

    I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
    I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
    Does anyone have any solutions?
    == QUOTED TEXT BELOW ==
    Re: Newbie: Connect Windows -> OSX Server
    Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
    I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
    For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
    Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
    The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
    On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
    Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
    Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
    Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
    Peter
    * The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
    minor version numbers, padded with zeros.

    Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
    http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
    http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
    I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

  • Snow Leopard server, Lion clients

    Good day I am running a 10.6.8 server (Mac Pro 2010) with 300 user account on it. At this time because out client computers needing compatibility with multiple applications upgrades we need to upgrade all out clients to 10.7.3. The decision has been made and I need to go with it. The server only runs user accounts, shared folders, Wiki and DNS. I am hesitant to upgrade the server to 10.7. I have attempted some quick searches for any issue with running 10.6.8 Server and 10.7 clients but it has not resulted in much.
    What is the biggest issue I am going to be running into?
    Will AFP still work with 10.7 clients?
    Should I upgrade the server to 10.7 also?
    What will I loose at this point upgrading everything?
    Looking forward to what I can learn.

    What is the biggest issue I am going to be running into?
    What issues will you run into if you upgrade your clients to Lion, but leave your server on Snow Leopard? none. That's entirely valid.
    Will AFP still work with 10.7 clients?
    Yes
    Should I upgrade the server to 10.7 also?
    Not unless you specifically need some of the features in Mac OS X Lion Server, and absolutely not if you only have one server.
    What will I loose at this point upgrading everything?
    Probably several nights' sleep. Upgrading a server, and maintaining all the services without any downtime is a significant process. Snow Leopard Server doesn't stop running just because Lion is available, and it won't stop when Mountain Lion comes along, either.
    If your mandate is to upgrade the clients, then do that, and take your time planning your server upgrade/migration.

  • Lion clients with Snow leopard Server

    Are there known issues with a Snow Leopard Server Mananging Lion Clients.  I currently manage 40 IMacs in two labs
    all running Snow Leopard, the only services I use on the Mac Server are Open Directiory, Print Services, AFP, and FireWall services
    the Server is a Mac PRo with 2x3.2 Ghx quad-Core Intel Xeon Processor and 32. GB RAM

    Snow Leopard can't serve AFP devices to Lion clients out of the box.  There seems to be a workaround, but I haven't gotten it working myself yet.

  • Can I use Snow Leopard Server with Windows clients?

    Mainly for e-mails and calendars. I have small office with 12 windows computers from XP to Win 7 and MS Office from 2003 to 2007. Will Snow Leopard Server work with that?

    Can Mac OS X Server do this?  Sure. 
    You're going to be learning a whole lot about running a server, regardless.
    You really need to sort out what you have here and where you want to be, and how to upgrade or replace yor migrate your environment, and before you add the substantial increase in complexity of serving Windows from Mac.  If you can't get off of Office circa 2003 or similarly old software, what are you going to do when you find, say, an incompatibility, or a need to migrate mail clients?     Who are you going to call for help?
    I'd guess that Small Business Server (SBS) is likely your best target here. 
    AFAIK, Exchange Server (which I'm guessing is what you're using) supports larger mailboxes in newer releases.
    Look at the sustaining costs for what you're considering purchasing, too.  How much it'll cost to configure, deploy and maintain the box and the network.  Up-front costs are an obvious consideration, but maintaining many boxes and many versions itself introduces costs.
    The arrival of Lion Server next month does not change my opinion.   (And I'm not usually suggesting Windows and Windows Server boxes, either.)  (And with the arrival of Lion and Lion Server, I'll follow my usual approach and not look to upgrade to the first release of that (or any other) new platform, if there are business-critical functions and services involved.  You need time to debug and test the deployment.)

  • Server Admin. file sharing lion client to Snow leopard server

    I'm running Lion on my client Mac and my Server is Snow leopard 10.6.8.  I have to use Server Admin 10.7 on Lion but there is no "File Sharing" tab to set up or edit the file sharing options on my 10.6 server?.  I understand this is correct for Lion Server, but how do I get round it for Snow leopard Server??  On the Apple website compatibility page (http://support.apple.com/kb/HT1822) it states:
    "Mac OS X Server v10.6
    To administer a Mac OS X Server v10.6-based server, you can use the Server Admin Tools 10.6 on a Mac OS X v10.6 (client) computer. You should match the version numbers of the server, tools, and admin workstation as closely as possible; for example, use Server Admin Tools version 10.6.8 on Mac OS X v10.6.8 to administer Mac OS X Server v10.6.8. You may also use the Server Admin Tools 10.7 on an OS X Lion computer to administer Mac OS X Server v10.6."
    So, How do I administer file sharing???

    To configure File Sharing on a 10.6 server using 10.7 Server Admin, click the service (AFP, SMB, NFS, etc.) then click the Share Points tab.

Maybe you are looking for