Leopard server networking

I haven't run any version of mac os server before, so most
of my frustration is probably lack of experience, but the
things I am trying to do are easy under linux and seem all
but impossible under leopard server.
My configuration:
I have a dsl connection from at&t that uses pppoe to
connect. They give me a /28 block (i.e. 16 ip addresses).
I am using a Mac Pro for the hardware.
What I want to do is the following:
1: Automatically start up the pppoe connection at boot time,
and re-connect if it goes down for some reason.
Q1a: How do i start or stop a network connection from the
command line?
Q1b: Where are the ppp options to the pppd process set?
Although I don't think i need it for my configuration, I may
need or want to set the proxyarp option. /etc/ppp/options
is a possibility, but it would be nice to set it only for this
particular connection, not all the time.
2: Attach additional IP addresses to the ppp interface
when it comes up so i can run more than one ip based
service on the same hardware.
I can do this via the command line:
ifconfig ppp0 alias <new ip> netmask 255.255.255.240 <at&t gateway>
And i can probably put this in a script at /etc/ppp/ip-up but
it seems like this would be configurable elsewhere.
3: As a side note, why can't the airport extreme basestation
distribute a range of addresses if it is connected via pppoe
the same as it can if connected via ethernet?

Yes, the Cisco is configure for NAT and works fine via the airport and can reach the Server after unplugging and reconnecting the server.
The Server has a static IP address have has the appropriate routes in the Cisco. Again this config worked fine until I upgraded. Additionally, I have a route for FTP traffic to the server from the outside interface.
Apple Firewall is disabled.
It's the strangest thing. If you disconnect the server's ethernet cable and reconnect it the server can be seen again on the network. At that point you can connect using remote desktop and stay on for as long as you wish. Once you disconnect from remote desktop the computer again disappears from the network as if the nic card has gone into hibernate mode. I have tried to change the setting to never sleep and Wake for Ethernet network access. under the Energy Saver utility. Any other suggestions? Is there a config file that I could play with that might help keep the connection alive?
To get the server back on the network, unplug and reconnect and it show that it has been idle for X# of minutes.
Appreciate your input.

Similar Messages

  • Question about changing a Snow Leopard Server network settings

    We have an Xserve running Mac OS X Server 10.6.8, the primary services running on it are afp, smb, dhcp, dns, jabber and the calendar sever.
    Right now we have a router connecting two networks together, 192.168.0.0/24 and 192.168.1.0/24. The Xserve has a static IP address in the 192.168.0.0/24 range.
    In order to combine two phone systems into one I am required to combine the above networks, this will involve removing the router and changing the subnet mask on every device from 255.255.255.0 to 255.255.254.0, any device that is currently part of the 192.168.1.0/24 network will also need to have it's router setting changed from 192.168.1.1 to 192.168.0.1. That part should all be easy.
    However, this is my first experience expanding a network past a standard class C and am wondering if there is anything I need to watch for on my Snow Leopard Sever.
    Specifically I wonder about dhcp settings, right now there are two dhcp servers, the Xserve which provides dhcp for 192.168.0.0/24 and the router that provides dhcp for 192.168.1.0/24. Once the router is removed the Xserve will need to provide dhcp for the entire network.
    Looking at the Xserve dhcp configuration right now I have one subnet defined providing addresses 192.168.0.5 to 192.168.0.125.
    Can I simply click the + to add another subnet and add for instance a range of 192.168.1.5 to 192.168.1.125?
    Will it simply give out all of the ip addresses in the first range and then start with the 2nd? Or do I need to find a single range of ip addresses large enough to meet my needs? (e.g. 192.168.1.5 to 192.168.1.225 or something).
    Is there anythign else to watch for after making this type of network setting change?
    Thanks in advance.

    Thank you for your very detailed reply.
    I understand the problems that can arise using 192.168.0.x and 192.168.1.x and if this were a new project I would definitely switch to something else, however in this case we have been using these ip ranges for years (they were in use here long before I started) and I don't want to have to redo all of my dns settings at the same time I make these other changes so I'm going to stick with the same ip's we are using at least for now. Anyone here needing vpn access has already dealt with this issue but we  have very few vpn users so it has not been a major problem for us to date.
    My biggest question is about increasing the size of the dhcp pool. For instance, after I change all the network settings and set up a /23 network is it possible to have a single dhcp pool that includes some ip's in the 192.168.0.x range and others in the 192.168.1.x range? I guess what I am asking is when I am in Server Admin and click on DHCP one of the tabs across the top is "Subnets". Right now there is a single "subnet" configured that provides addresses from 192.168.0.5 to 192.168.0.125.
    Ideally I would like one dhcp pool that provides ip's in the range of 192.168.0.5 to 192.168.0.125 and then if all of those are used up, moves to 192.168.1.5 to 192.168.1.125. Can I do that by simply adding another "Subnet"  so there are two? Or do I have to find one larger single range? (e.g. 192.168.1.5 to 192.168.1.225?) You may have already answered this indicating I have to have a single larger range but I just want to be sure.
    The parts about changing subnet masks, and routers and all that I think I have a pretty good understanding of.
    Your last paragraph is something I have been worried about, I do have a feeling that after making this change there will probably be unforseen issues that will need to be resolved, I'm just hoping it is not too many. For the scope of this thread I will just focus on issues that may arise with the Snow Leopard Server however.
    Again, thank you for your help.

  • Logging in to my Leopard Server network keeps failing

    This keeps happening - it's almost as if the OD or AFP services are dying after a while (although they seem still to be running). What happens is that suddenly a client on the network cannot connect to a sharepoint as a registered user (guests seem OK). Any valid login just gets rejected. If I reboot the server then the client can login again. I haven't had time to investigate whether restarting the services resolves the problem, but whether it does or not there seems to be a problem on the server.
    Can anyone throw light on what may be causing the login capability to keep dying?
    This is really annoying, because I have been using Tiger Server happily for 3 years and fell for the marketing to upgrade to Leopard Server (which feels more and more to me like a beta release).
    Thanks,
    Ian.
    --

    @Strontium, not sure what the basis for your opinion is, the server login processes *is* a client of  OpenDirectory and Kerberos and subject to the same PAM authorization process and thus the creation of a Kerberos ticket.
    After nearly two days of digging, I found the issue was caused by the existance of user records for some of my network users in the /Local/Default directory on the server which had  an AuthenticationAuthority value pointing to an old, no longer used, Kerberos domain.  As these were OpenLDAP users, I hadn't even thought of examing the local directory until I noticed that the expected Kerberos ticket behavior was working properly for one of my accounts which was not a 'mobile' account.  I then realized only my 'mobile' accounts (which were nearly all of them) were the only accounts showing this problem. 
    I believe what happened is when I changed server's kerberos name at some point in the past (by backing up the OpenLDAP records, demoting the master, re-creating the master with the new Kerberos name, importing the records, and resetting passwords); I never thought to clean up any locally cached user records for my 'mobile' users.
    To fix: I used the Directory Utility to delete the users from the local cache.  On next login by a mobile user, a correct local user record was created reflecting the proper Kerberos authority and now I'm getting Kerberos tickets on login again. 

  • IPod Touch and Leopard Server network

    At school we have staff and students beginning to explore iPod Touches as a classroom resource. There is no problem getting them to use the school's AirPort network, but some apps, such as Google Earth will not run.
    I'm wondering if anyone has experience of using iPod touches in a Leopard Server environment and if they have any tips or hints to share please?
    Brian Bowell
    ICT Support
    Berkley School
    Hamilton
    New Zealand

    Hi Brian,
    You really should have to do anything specific on your network to make the touch work with Leopard Server. Here are a few questions to point you in the right direction:
    Are you seeing any specific error messages?
    Are you blocking any ports on your network?
    Have you looked at the log files from a device that is exhibiting this behavior?
    Good luck,
    Jon

  • No Ethernet/Internet Connection on Parallels 7 Running Snow Leopard Server - Fix?

    I have recently installed Parallels 7 on my 2013 iMac, and have both Snow Leopard Server and Windows 7 running great on the Parallels platform.
    However, after installing some anti-virus software, "ClamXav" and "MacScan", I need to have the internet connected to my Paralells 7 so I can receive viral updates to both these programs. I am unable to get any ethernet/internet connection on my Paralells 7 running Snow Leopard Server.
    I have tried to update the Paralells 7 Snow Leopard Server "network Info" (in SL systems preferences" ... as the same ethernet connection info that I have running my "network connection" on my main OS Mountain Lion, but still no ethernet connection in Paralells 7.
    This is a screen grab of the locations where I believe I am able to update my "ethernet" info for Paralells 7 Snow Leopard:
    Obviously, I've blurred out the current info in these two windows, for security purposes, but exactly what should be applied to these windows to get my "ethernet" connection in Paralells 7 up and running?
    I would think entering the exact same "network info" as appears in my Mountain Lion "Systems Preferences - Network" window, would get me internet connected on Paralells 7 Snow Leopard? Evidently not ... what is needed for me to get this right?
    Anyone have experience getting "ethernet/internet" connected on Snow Leopard Server, using Paralells 7?

    MlchaelLAX
    Since I have been directed to: "NOT waste everyones time on this discussion"  the only thing more I am going to do after this post is click on: "Stop email notifications" and never return to this thread again!
    Internet access through Ethernet in Snow Leopard Server installed into Parallels 8 on 2011 Mac Mini in Lion:"
    I simply don't want to purchase and have to install Parallels 8 .... Parallels 7 should work fine on connecting to the Internet. Also, I was asking about the internet connection issue with the new 2013 iMac (running Mountain Lion 10.8.3 runiing Parallels 7), not a 2011 Mini Mac running Lion with Parallels 8.

  • How to resolve network issue or dns to access web page on snow leopard server?

    I have my network setup like as follows:
    internet > router 1 > ethernet ports > switch > router 2
    I have a mac osx snow leopard server connected to "router 1", but it is so slow when accessing a web page hosted on the server from a browser on a workstation connected to either router 1 or router 2?
    Is there a problem with my network setup or maybe because I changed the name to newservername.local?

    @Jeff and @Camelot,
    I think it is a DNS issue.  I completely reset the DNS settings on server and the local name with the steps below, but now cannot access the site hosted on the server at all
    I used a modified version of http://www.mkahn.com/2010/09/configuring-dns-on-mac-os-x-10-6-snow-leopard-serve r-for-hosting/ to reset the server set
    1.  Stop DNS Service in Server Admin
    2.  Close Server Admin
    3.  Obtain 10.6 DNS Default files (below)
    4.  Overwrite the DNS files with DNS Default files:
    /etc/dns/loggingOptions.conf.apple
    /etc/dns/options.conf.apple
    /etc/dns/publicView.conf.apple
    /var/named/named.ca/etc/named.conf
    /var/named/named.local
    /var/named/localhost.zone
    5. Restart your server
    All machines have 1ms ping responses within the network including this snow leopard server that I am trying to setup.  There is another test web server that return pages instantly within this network so I doubt it is a network issue, but a DNS issue.

  • How to set up Leopard server on a wifi-only network?

    Hi - I'm having a lot of trouble getting Leopard server installed and running on a wi-fi only network. Standard setup says I have to be connected to a local Ethernet. Advance setup allows me to start services, but then the server disappears after a few minutes.
    Anyone able to do this successfully?

    Per the documentation, there is no way to do this. Leopard Server requires a dedicated Ethernet port on the subnet that it serves - so I'll have to bridge my Ethernet and wifi networks. As I don't have a hub of my own, I'll upgrade my Airport Express to an Airport Extreme, connect the mini and see if the services come back up or if I have to reinstall.
    Tim

  • 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.

  • New Snow Leopard Server, Slow Network Accounts

    We've installed Snow Leopard Server on our XServe quite a while ago and since then all users who work with network accounts are complaining about serious perfomance issues. These issues are for instance logins which may very well take up to several minutes, or applications like Adobe InDesign which take their time to load files from the users network shares.
    Our System consist of:
    1 XServe running OS X 10.6.8 Snow Leopard Server
    48 iMacs running OS X 10.5
    1 Windows Server 2008
    The XServe serves as an OpenDirectory and Fileserver, while the Windows Server delivers DNS.
    We have created ~500 users and 25 groups in the OpenDirectory. All user files are located in their roaming profiles on the Xserve. Additionaly every user has access to one group folder, which is located on the Xserve as well.
    All group folders are Sharepoints and added to the dock of all users in the appropriate group.
    I have already checked DNS settings, user accounts, network connectivity in general, network load during peak hours, the ACLs on the group folders....
    By now im simply out of ideas what my cause the problem, let alone how to solve it.
    Any hints are greatly appreciated.

    Are you using any redirections?  Redirecting the cache folder from the network home to the /tmp should improve speed.  Use this white paper from apple.  http://images.apple.com/education/docs/Apple-ClientManagementWhitePaper.pdf The redirections are on page 53.

  • Sharing Canon Wireless Network Printer on Snow Leopard Server

    Trying to setup a wireless printer to share on the LAN via Mac Mini Snow Leopard Server, however the sharing option is not available.
    Configuration:
    Mac Mini Snow Leopard Server (latest updates etc.) (static IP)
    TimeCapsule Wireless network (static IP)
    Canon MP620 Wireless printer (static IP)
    Two MacBook's (DHCP)
    Printer drivers (network drivers, and scanner drivers) from Canon installed on Mac Mini and printer is connected and setup via wireless network on Mac Mini; it is operational and can print from Mac Mini directly without problem
    Sharing option on Mac Mini for the printer is missing in Print Settings (missing checkbox), so unable to share the printer on MacBook's via the Mac Mini, also under Sharing Settings the printer option is not there (assuming because share this printer option is not in the print settings)
    Ideally, I want to setup the printer on the Mac Mini as a print server, without having to hardline (USB) the printer to the Mac Mini.
    Thanks for any help, ideas etc.

    Hello and welcome to Apple Discussions.
    On OS X Server, you need to use the Server Admin utility (Applications > Server ) to share the local print queue. This requires the Print service to be added/started and then a queue created for the local printer.
    Seems unusual that you would want to share a wireless printer from the server. The MacBook 'clients' would still be able to connect directly to this printer without having to connect via the server share so without knowing all the details of your setup it just seems an odd requirement.

  • I transferred files from a NAS server to the Mac Mini Snow Leopard Server and now some of the files have Custom Access and can't  be opened by some users.  How do I fix this?

    We're setting up our Mac Mini Snow Leopard Server, and in the process transferred files that had been stored and accessed from our Blackarmor NAS server over to the Mac.  These files were all created on PC's and are Office Excel files, WordPerfect files or PDF's.  When you look at the files on the Mac from the Mac and bring up Get Info for the affected file, it says that the file has Custom Access.  The files that work properly don't have that configuration.  I can access and open the files on some computers, but some users can't open the files from their computer even though they can see it.  We're all using PC's and they get the Error:  Access Denied-Contact your administrator--or something similar.  I've seen on the web similar issues and it may have something to do with ACL permissions.  I don't know enough about Mac OS to understand this, but what is baffling is that they can be opened from some PC's but not others, and all of the Users have the same accessibility to the files.  Thanks for a solution!!

    Oh, on the losing Internet, try this...
    Make a New Location, Using network locations in Mac OS X ...
    http://support.apple.com/kb/HT2712
    10.7 & 10.8…
    System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
    10.5.x/10.6.x/10.7.x instructions...
    System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
    The interface that connects to the Internet should be dragged to the top of the list.
    Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.
    For 10.5/10.6, System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...
    208.67.222.222
    208.67.220.220
    Click OK.
    PS. Your English is quite good & completely understandable.

  • Setting up Snow Leopard Server with Address Book, iCal for Small Business

    Hello Folks,
    I have a small business with 2-3 people and I want to setup Snow Leopard Server on a Mac Mini. I have everything in place, RAID, Backup drive etc.
    What I need is a guide on how to setup the server correctly and how to setup Address Book Server, iCal Server, DNS, etc. I was in IT a long while back but have gone back to my creative roots and sworn off IT but I am in a situation where my IT guy's wife is pregnant so he is busy painting the baby's room, etc.
    I was looking at Snow Leopard Server for Dummies and a few other books. Do you guys have any suggestions on resources for me to read or research that would give me very straightforward steps in getting this setup. I am at a point where I can re-install from scratch if needed.
    For the ease of those that might respond let's assume I know my way around Mac and general networking as a whole.
    Thanks in advance for any advice.
    Cheers,
    Jason

    Hi Guys,
    First of, I will give you a brief background on me regarding networking as a mac user since 1994. I can setup and network multiple macs without a server in our home and small office. Turning file, print and internet sharing with a regular Mac OS X client version at no problem at all. This would be my first time setting up a Mac OS X Snow Leopard Server.
    I'm in the same boat as Jakekub but we do not have a static IP from our DSL provider. We just bought a Mac Mini Server for our small office with 3 iMacs and 1 MacBook. We will just use the server for internal usage and to centralized things out and use some of server's features like Address Book, Mail, iCal etc. I've search the forums and found Orhidy's post here:
    http://discussions.apple.com/thread.jspa?threadID=2148553
    I even followed the sample IP Address, Subnet Mask, Router, DNS Server and I think I had it correctly setup initially. And I think I got it all running on the basic setup base on his instructions. So I tried to test my DNS settings via Terminal > hostname then got answer as
    servername.companyname.private
    And double checking DNS again with a command: sudo changeip - checkhostname and was given an answer of:
    Primary address = 192.168.1.192
    Current Hostname = servername.companyname.private
    DNS Hostname = servername.companyname.private
    The names match. There is nothing to change
    dirserv:success = "success"
    But here's another one that bugs me. I tried to follow from "Mac OS X Snow Leopard for Dummies" the command line:
    NSLOOKUP hostname
    and got an answer of:
    ;; Got SERVFAIL reply from 192.168.1.192, trying next server
    Server: 192.168.1.1
    Address: 192.168.1.1#53
    ** server can't find hostname: NXDOMAIN
    So does it mean that I still haven't configured my server properly?
    Thank you all for the help in advance!
    dive

  • Snow Leopard Server running extremely slow all of a sudden!!

    Hi, I'm not a qualified server technician but am currently trying my best to run a server in a Secondary School! Please help, need to fix ASAP.
    So basically we've got a Mac Pro running Snow Leopard server which has become incredibly slow in the past week. Nothing has changed in our department to trigger this. Here's everything I know so far...
    - If I try to log on to the admin account when "Some Network Accounts Are Available", log on will take under a minute. If I try to log on to the admin account when the light goes green and "Network Accounts Are Available" log on will take forever and eventually just crash and which point I have to just force a shutdown and try again.
    - When I can log on, some aspects of the computing seems fast and other aspects are really slow. For example, a few programs open as soon as I log on no problem, however a simple spotlight search or trying to open Sytem Preferences will crash the computer completely.
    - Have tried booting in Safe Mode, and everything ran fast and how it's mean to but once restarting and booting normally the problems remained.
    Sorry for the lack of knowledge!!
    Thanks in advance.

    Your comment indicates "crash the computer"?  Do you mean that OS X Server itself fails, and you have to reboot?  Or that the application crashes, and you have to restart it?
    The following are some general approaches toward gathering some data:
    Launch Console.app from Applications > Utilities and see if there are blocks of repeating errors.
    Launch Terminal.app from Applications > Utilities and issue the following harmess, diagnostic command:
    sudo changeip -checkhostname
    After entering an administrative password and possibly seeing a one-time informational message about sudo, you should see some network configuration information and then an indication that no changes are required, or that there are DNS or network errors.
    Boot from the Snow Leopard installation DVD and run a volume verification pass using Disk Utility, this from the Utilities menu of the installation disl.
    FWIW...
    If the applications or OS X Server are crashing, then you're generally heard toward either a reinstallation of the software, or a hardware repair, or quite possibly a combination of the two.
    Forcing a hard shutdown can lead to corruptions, depending on exactly what's going on when the power drops out; that's probably best left as a last-resort approach and one best avoided.

  • Can I use Leopard Server for a few things without a static IP/DNS mapping?

    Caveat: I'm pretty capable at setting up and running macs, but not a crack server admin or anything like that. I don't write code and my eyes start to glaze over when you start talking about Kerbos and the like...
    Question: I'd like to use Leopard server for a few things on my local network - with some vpn access to the same services:
    - iCal server (the most important feature) for 3 users
    - File server services for Time Machine (yes, base Leopard can do this)
    - vpn access into the iCal server for one user
    Do I have to go through the headache of switching over from a dynamic IP to a static IP, setting up DNS mapping, etc? Or is there a simpler way?
    Any help appreciated. Thanks

    Caveat: I'm pretty capable at setting up and running macs, but not a crack server admin or anything like that. I don't write code and my eyes start to glaze over when you start talking about Kerbos and the like...
    Question: I'd like to use Leopard server for a few things on my local network - with some vpn access to the same services:
    - iCal server (the most important feature) for 3 users
    - File server services for Time Machine (yes, base Leopard can do this)
    - vpn access into the iCal server for one user
    Do I have to go through the headache of switching over from a dynamic IP to a static IP, setting up DNS mapping, etc? Or is there a simpler way?
    Any help appreciated. Thanks

Maybe you are looking for