Cannot do a SL Server 10.6 remote install

Hi!
I'm a newbe to the server environment and came to a halt emediately in trying to learn. I follow the Mac OSX Server Essentials 10.6 book and the first step is to do a remote install from another computer to the server, in my case a Mac Mini.
I can initate the installation process, e g the Mini and my MBP is connected and I can use Remote Install to let the Super Drive in the MBP deliver data to the Minin Server via my Network Switch.
When that process is ready, the Mini server is supposed to show up in the Server Admin window on my MBP to let me coninue the remote install. But it will not show up in the Server Admin window.
I checked that the Mini is "visible" in the network and it is, I used Network Utillity to check.
I done it from scratch several times but the Mini server will not show up in Server Admin on my MBP.
What am I doing wrong?
Smigge

Mac OS X Server requires a static IP address, and functional DNS. Full stop.
Unless you have sufficient public static IP addresses for your network (or if you're fully running IPv6), you'll be using private IP addresses and private DNS services.
You'll likely want to set up in a subnet in 10.0.0.0/8 or 172.16.0.0/12, and out of 192.168.0.0/16, as you'll eventually want VPNs, and VPNs depend on IP routing, and coffee shops and home networks tend to be in a few subnets in 192.168.0.0/16, and having the same subnet on both ends of the VPN makes for routing problems. Best not to start out with a subnet that can cause issues later.
Unless you're running public IP, you'll want to [set up your own DNS services|http://labs.hoffmanlabs.com/node/1436].
SRV records are generally unnecessary.
I'm here presuming you're not doing public-facing mail; that adds some complexities here.

Similar Messages

  • Cannot start the SQL server service after you install Active Directory

    Good Morning,
    Im the system admin for a small company.  We have a dedicated domain controller but it is the only one.  To get a second domain controller up and running on our domain, I installed the AD role on our file and SQL server.  After the reboot
    we couldnt get SQL up and running.  I found this article
    http://support.microsoft.com/kb/929665
    In the article it reads
    To work around this issue, repair Windows Internal Database. To do this, run the following command line at a command prompt:
    Msiexec /i SSEE_10.msi CALLERID=OCSetup.exe REINSTALL=ALL REINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v <var><Log_File_Path></var>
    My question is what is the Log_File_Path?  Is that where I installed the AD log path?
    My DBA is also looking into this as well.
    Thanks in advance,
    Brian
    Brian Fink, MCSE

    Hi Brain,
    what's version of SQL Server that you have installed and what's your operationg system version info?
    If you are running SQL Server 2008, which is not supported on the Windows Server 2008/2008 R2 domain controll (DC), even on Windows Server 2003 DC, there are limitations. Microsoft does not recommend to install SQL Server instances and DC on the same server,
    for more information, see Install SQL Server on a Domain Controller (http://msdn.microsoft.com/en-us/library/ms143506.aspx#DC_Support).
    There are some threads in the forum talked about installing SQL Server and DC on the same server, here are some for your references:
    http://social.technet.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/1a2963ff-90d7-4bba-97ce-fa15f70fb6a8/
    http://social.technet.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/981ef726-d04a-4063-8008-cc7bbad854ab/
    Hope this helps. Please feel free to let me know if you have more questions.
    Best Regards,
    Chunsong Feng [MSFT]
    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Using server assistant to remotely install/configure Leopard.

    As I don't have a graphics card in my Xserver, I need to configure Leopard remotely.
    I already installed Leopard Server using Target Disk Mode, but I can't find a way to configure it.

    You should just be able to run Server Assistant on another Mac on the local network.
    It should reach out to find the server and allow you to configure it over the network.
    Are you saying you've tried that and it's not working?

  • Cannot connect to iCloud server on iPad after installing latest update

    I cannot access iCloud through iPad since installing latest update. Keep getting Accept the new terms etc" but can't do so through the setting s page

    When I go to the settings page to access iCloud and click on terms and conditions it gives the message

  • Cannot Connect to B1i Server, The Remote Server Returned an Error 401

    Hi,
         I have installed the integration package ( Without any errors in the installation) and when I connect to SAP B1 I am getting an error msg "Cannot connect to B1i Server. The Remote server returned an error : (401) Unauthorized" And I am not able to view Dasboards.
    Thanks in Advance,
    Dasari.

    Hi Dasari,
    When I had installed, this thread helped me out a lot, you should give it try also -
    Re: remote server error: (400) bad request. installing  Cockpit
    and this
    [Guide Deleted 31 OCT 2011 - Contained Out of Date Information]
    Edited by: Jason Lax on Oct 31, 2011 10:44 AM

  • Remote Desktop cannot verify that this server belongs to the same server farm

    Hello Team,
    I am running Windows Server 2012 in my environment. I have 2 RDS Servers which are configured for load balancing. RDP to these hosts works just fine. But when i connect to any published remoteapplication , it gives me an error
    Remote Desktop cannot verify that this server belongs to the same server farm.
    What am i missing here, kindly suggest.
    Binu Kumar Small Business Server Support

    Hi Binu,
    Do you have any progress?
    If not, please make sure that the RD web access URL is configured as the farm name on each Remote Desktop Session Host server.  
    Here are some related threads below for you:
    TS Web with TS Farm on W2K8 servers
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/09715e58-6e52-4c39-b445-4aa8fbc31cb0/ts-web-with-ts-farm-on-w2k8-servers?forum=winserverTS
    RD Session broker issue; Cannot connect to one of the host servers through RDC
    https://social.technet.microsoft.com/Forums/sharepoint/en-US/b9c15a01-a9cb-4793-8758-acd2e60ae7a5/rd-session-broker-issue-cannot-connect-to-one-of-the-host-servers-through-rdc?forum=winserverTS
    RemoteApp - Cannot verify computers belong to the same server farm
    https://social.technet.microsoft.com/forums/windowsserver/en-US/40be1eda-f752-4b64-bb47-dbe2156218f9/remoteapp-cannot-verify-computers-belong-to-the-same-server-farm
    Best Regards,
    Amy
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]

  • Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer

     Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer, And when Installing network printers from the domain controller it reports it cannot connect to printer.  I can ping all
    network devices. I can connect to the internet.
    On boot I get a netlogon 5719 error followed by service control manager errors 7023,7001 and a group policy error 1129.
    Clients can connect to the remote application and RDP operates to connect to the server internally and externally.
    The domain controller is another server 2008r2 box. I have scoured the internet but have not found any solutions that work yet.

    Hi,
    After referring to your post, it can be identified that the issue which you are facing is mostly due to some network issue in your environment. Please recheck your network connection issue between computer and domain controller. 
    Can you able to ping with IP address and also with fully qualified name of a domain controller in the users' and computers' domain. If it fails states that name resolution issue with computer and domain controller. Are you using MS DHCP Relay agent then there’s
    available Hotfix for the particular Event ID. Please go through this KB 2459530 to fix the error event ID.
    As per the net logon error 5719 which you are facing states that the client component of Netlogon was unable to locate a DC for the domain it was trying to perform an operation against. Below is one of the reason. If this is being logged on a DC and the event
    refers to the DC's own domain, something might be preventing the client component of Netlogon from starting a network session (to itself or to another DC in the domain). The following event 7001 & 7023 states start & stop operation service. Please
    go through beneath article for more details.
    1.  Event ID 5719 is logged when you start a computer
    2.  Netlogon 5719 and the Disappearing Domain [Controller]
    3.  Event ID 1129 — Microsoft-Windows-GroupPolicy
    Hope it helps!
    Regards.

  • Server 2012 RTM Remote Desktop Connection Broker Role Won't Install

    Hey guys,
    I have been searching for and trying fixes for this for 3 days, and I've gotten no where.  Thanks in advance for trying to help me out.
    Here's the situation:
    I have a brand new installation of the Windows Server 2012 Datacenter 64-Bit RTM from MSDN.  This is my one and only server (just my personal one for home), so I'm using this single server to run all of the services that I need.  After a fresh
    installation, I added the AD and DNS roles and promoted the server to the PDC.  Then I go to add the Remote Desktop Virtualization Services (the VM virtualization role).  The installation fails, but I can't find any explanation as to why.
    I've wiped out the OS and reinstalled from scratch at leat 15 times, trying various combinations, fixes, approaches, etc.  including powershell, Remote Desktop Services Deployment, standard role-based deployment, etc.
    Using the role-based deployment, I can get every 'Remote Desktop Services' component to install except the Remote Desktop Connection Broker.  I've tried enabling RDMSUI_TRACING, but didn't get any information at all as to why it's failing.  I also
    cannot find RDMSDeploymentUI.txt log.
    I've also tried to deploy this using Powershell using this command:
    New-SessionDeployment [-ConnectionBroker] <string> [-WebAccessServer] <string> [-SessionHost] <string>
    That particular item does provide some error messages, but they seem to complain about the Session Host not being able to install due to not being able to find the connection string key in the registry for the Windows Internal Database.  However, I can
    get the session host and every other component to install using role-based deployment, except the Connection Broker.
    I've run an SFC scan, which found no issues.   I've also tried applying the one update available in Microsoft Update, and tried it without applying that update (reinstalling between attempts of course).
    I'm completely at a loss.  Has anyone encountered this before?  Any suggestions would be greatly appreciated.  Is there a powershell command for just installing the Connection Broker that might provide some additional error information, or any
    information at all?
    I would greatly appreciate any help anyone could offer.  I'm willing to try anything.  Thanks for taking the time to read this.
    Sincerely,
    Dominick

    Also Found this:
    1. You try to install the Remote Desktop Connection Broker (RDCB) on a server that also has the Active Directory Domain Server (domain
    controller) role installed. This configuration is not supported by Microsoft. You need to install the RDCB on a server that does not have this role installed. See: Remote Desktop Services role cannot co-exist with AD DS role on Windows Server 2012 http://support.microsoft.com/kb/2799605
    2. If you don’t have the Active Directory Domain Service install, this issue might be caused by the Windows internal database (WID) that
    the connection broker installs and the Windows Update KB2821895. If you have KB2821895 installed, unfortunately you can not uninstall this KB. Try to install the Remote Desktop Connection Broker (RDBC) role on a server that does not have this Windows update.
    Note: There is currently no official communication from Microsoft that here is an issue with RDBC and KB2821895. However, try the RDBC installation
    without this KB and see what happens.
    For more information, Refer below link...
    http://fabrikam.wordpress.com/2013/07/15/connection-broker-installation-failedremote-desktop-deployment-issues/

  • 2010 Mac mini server remote install OS X failure

    I tested re-installing OS X remotely to my 2010 Mac mini server. It worked the first time. I got to the installation process, and abandoned it without actually doing anything.
    But when I tried again, it failed, and I have not been able to get it to work ever since. I went to a local Apple shop and tested at its Genius bar. People there cannot figure out the problem. They exchanged my unit for a new one.
    I took the new unit home, tried, and it failed again. Then I called Apple Care. They cannot pin-point the problem, but suspected that, since I failed with two units, the problem may be with the computer that has the DVD. I am not sure about his. Here I post my story for help. The details:
    1. The OS X Server installation DVD (which came with the mini) was put in a 13" 2009 Macbook Pro. There I ran the Remote Install OS X application. Selected the Installation DVD.
    2. Then I started the Mac mini server, holding the down Opt key. The Installation DVD appeared from my local network. However when I selected the DVD and clicked the arrow sign under it, things went wrong. A circle with a line segment appeared briefly (indicating a problem, I think). Then the mini simply went to boot from its own hard drive where the original OS X was.
    Help and suggestions are very much appreciated.
    Additional information:
    Remote Disc works fine. From my Mac mini, after booting into the original OS, I can see and open DVDs in the Macbook Pro.

    Target disk mode method works fine. I can boot my mac mini from its installation DVD placed in my macbook pro, connected to the mini through firewire. So I don't think there is any hardware problem.
    I played with a few other things. First I used another DVD, this time the one that came with my 2009 macbook pro, a non-server version OS X. When I tried to remote install it to my mini, the mini can still see the DVD but it hung after I chose to boot from it. It just showed a big circle with a line segment. It did not revert to boot the OS on its own hard drive.
    Next I again ran remote install on macbook, but booted the mini to its own hard drive. From there
    I changed its start up disk to Network Startup, and rebooted. The mini can find nothing on the local network.

  • Error: "Cannot access the web server" with BlazeDS Turnkey

    Help! I'm new to Flex and BlazeDS and Eclipse.  I was trying to setup a Flex Project using a BlazeDS/Tomcat server running from Eclipse on Windows XP per the example in flexbandit.com/archives/55#comment-269 and in (www.infoq.com/articles/blazeds-intro).   I am NOT using the Eclipse Flex plug-in.  I'm using Flex Builder for the Flex code.
    Here's what I've done:
    I installed BlazeDS and tested http://localhost:8400 - That worked.
    I setup Tomcat in Eclipse.  -  That seemed to work.
    I created a Dynamic Web Project in Eclipse - That seemed to work.
    I created the bare-bones BlazeDS Configuration under the Eclipse project and then created a basic HelloWorld java class.
    I added the destination in the “remoting-config.xml” file found in the c:/projects/workspace/ReportGenTool/WebContent/WEB-INF/flex” directory:
    <destination id="HelloWorld">   <properties>  <source>HelloWorld</source> </properties> </destination>
    When I started the application server by clicking on the server's green play button in Eclipse and then tried to open localhost:8400/ReportGenTool, I got the 404 error : The requested source (/ReportGenTool/) is not available which according to the instructions is fine.
    Next I created a Flex Project, but when I try to validate the new Flex project configuration, it gives me an error "Cannot access the web server. The server may not be running, or the web root folder or root URL may be invalid."
    When I validated the server was running after setting up the BlazeDs Turnkey, I saw the BlazeDS page.
    Now when I bring up http://localhost:8400 I get:
          Directory Listing for /
          Apache Tomcat/6.0.14
    My eclipse project is named ReportGenTool and I've overwritten the WebContent directory with the META-INF and WEB-INF directories from the BlazeDS installation (C:\blazeds\tomcat\webapps\blazeds).  According to Eclipse the server is running.
    My Flex project is named ReportGenTool and is located in another directory away from the Eclipse project directory.
         My root folder is: C:\Projects\workspace\ReportGenTool\WebContent
         Root URL: is http://localhost:8400/ReportGenTool/
         Context root is: /ReportGenTool/
    Any idea what might be wrong? What didn't I configure that needs to be configured?
    Thanks in advance.

    This is not working because your router has a direct to your web server that is not through the outside interface which is needed for nat to occur, for this to work you need to setup a loopback interface as nat outside and policy route traffic to there for your server traffic
    Bu if your server is internal why do you need nat at all? Can you not use bind with views that might be simpler
    M
    Sent from Cisco Technical Support iPad App

  • RD Gateway Manager cannot connect to local server

    Hi,
    I've come across a problem today where I'm unable to connect to our locally hosted RD Gateway server. We have one Server 2012 R2 machine with the Remote Desktop Services installed. The system was setup following the configuration wizard in Remote Desktop
    Services section of Server Manager. One of our users has gone to connect to the main remote app hosted by this setup and received an expired certificate error. No problem I thought, checked the certificate on the server and it does indeed expire today. I'll
    re-issue a self signed certificate through the RD Gateway Manager and all should be ok. On loading the RD Gateway Manager, clicking Connect to RD Gateway Server and selecting Local Server I get the following error.
    "The RD Gateway Manager snap-in console cannot connect to the server "SERVER" because it is not a RD Gateway server."
    I've checked that the services for remote desktop are running which they are, and I can connect to the server using standard RDP remote desktop.  Any ideas on where to go next to solve this problem?
    Rob

    Hi Rob,
    It seems the issue related to certificate as can’t properly configured. You need to import the certificate and store in local computer/personal store. Please check below article and verify the steps for certificate and other related setting,
    RDS: The RD Gateway server must be configured to use a valid SSL certificate
    https://technet.microsoft.com/en-us/library/dd320340(v=ws.10).aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Cannot connect to sql server after re installing IIS 6?

    I re installed IIS 6, after the restart i couldn't connect to sql server engine nor seeing it when using browse for me, i was trying to install team foundation server, at first it could see that i have an sql server running after re installing IIS it can't
    see it also. I'm using windows server 2003 SP2. Also i cannot remotely access it after the re installation  

    Just type the IP or name of the server (localhost) and try to connect.. SSRS 2005 requires IIS but how does it relate to SQL Server connection?
    What error are you getting? Make sure that SQL Server is running up.
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • [SOLVED] Cannot connect to NFS server.

    I'm trying to setup a NFS share at home. I have one laptop configured as a server, and one desktop client. Both are running Arch. I can ping both in either way.
    For some reason, I cannot connect to the server. At one time, I could connect, but only while having an empty /etc/hosts.deny file (which obviously is very insecure). Now, I cannot even reproduce this.
    Thus, I believe the problem is caused by either /etc/hosts.allow or / and by /etc/hosts.deny.
    Here is my server's /etc/exports:
    /shared 192.168.x.xxx(rw,sync,no_subtree_check,no_root_squash)
    And here its /etc/hosts.allow:
    ALL:192.168.0.0/255.255.255.0
    And finally its /etc/hosts.deny:
    ALL: ALL: DENY
    Running 'rpcinfo -p' on the server shows output, while running 'rpcinfo -p <server-ip>' on the client prints out 'No remote programs registered.'
    From what I've read, when the client wants to connect to the server, the server first checks in hosts.allow to see if the client's allowed to connect. So in my case, it should be able connect.
    However, when I run
    sudo mount -t nfs 192.168.x.xxx:/ /mnt/SERVER
    it tells me
    mount.nfs: mount to NFS server '192.168.x.xxx:/`failed: RPC Error: Program not registered
    And even if outcomment both hosts.deny and hosts.allow, running the same command prints out
    mount.nfs: access denied by server while mounting 192.168.x.xxx:/
    I'm clueless. Any help would be greatly appreciated!
    Last edited by MrAllan (2009-03-20 15:05:24)

    tomk wrote:
    Missed a detail on first reading. Your server's exports file makes the /shared directory available to 192.168.x.xxx, but your client mount command tries to mount the server's / i.e. root directory. You can only mount directories that have been exported.
    btw, there's no need to conceal internal addresses like that - we all have them, and there's no way anyone can use them to track you down. My laptop address is 10.12.62.99, my server is 192.168.10.10, and my irssi/bittorrent/whatever machine is 192.168.10.69. I challenge anyone to hack me.
    But if they know his IP, couldn't they use the lan IP to gain access easier than if they didn't know the subnet addresses? Since the thread is solved, I figured I would ask since I've always wondered about it.
    Btw, for anyone have unresolved NFS issues, see this bug report. The arch devs aren't responding to it for some reason, can anyone tell me why?
    http://bugs.archlinux.org/task/13434

  • Sharepoint list dataheet view error "Cannot connect to the server at this time. You can continue working with this list, but some data may not be available"

    I have a List which is having around 14000 items in it.while opening that list in datasheet view it is giving error .
    Below is a summary of the issue:
    After selecting datasheet view beow error occurs:
        "Cannot connect to the server at this time.  You can continue working with this list, but some data may not be available."
        "Unable to retrieve all data."
        The item counts displays say 100 out of 14000 items.
    Exporting List to excel is giving only 2000 records out of 14000 records.
    Other Observations   -  
    This is happening to only one list on the site .There are other lists in the site whose no. of records is equal to 8000 to 9000.They are working absolutely fine without any error.
    Also, If I am saving this list as a template and creating another list with it ,then it is working absolutely fine with 14000 records,so the issue does not seem to be related with no. of records as the template list is working fine.
    I have checked the Alternate access mapping setting ,its fine.
    It should not be related to lookup,datefield or any other column as the list created from it template is working fine with all these columns.
    I checked below links also ,but doesn't seem to work in my case.
    http://social.technet.microsoft.com/forums/en-US/sharepointadminprevious/thread/974b9168-f548-409b-a7f9-a79b9fdd4c50/
    http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/87077dd8-a329-48e8-b42d-d0a8bf87b082
    http://social.msdn.microsoft.com/Forums/en-US/sharepointgeneral/thread/dc757598-f670-4229-9f8a-07656346b9b0

    I have spent two days to resolve this issue. Microsoft has released two KBs with reference to this issue...but are not appearing in search results at the top.
    I am sharing my finding.
    1. First install the
    KB2552989 (Hopefully you might have already installed it. The KB detetcts it and informs the user.)
    2. Then update registry by adding new key for data fetch timeout as mentioned inKB2553007
    These two steps resolved the issue in our environment. Hope it might help others as well.
    Pradip T. ------------- MCTS(SharePoint 2010/Web)|MCPD(Web Development) https://www.mcpvirtualbusinesscard.com/VBCServer/paddytakate/profile

  • Jabber for Mac 9.2.1 Cannot communicate with the server

    Hi All,
    I'm using Webex and the Jabber for Mac 9.2.1 client that was automatically pushed.  I see "Cannot communicate with the server" when I attempt to login. 
    The same credentials work correctly when using the 8.6.5 client version.  I've attached the problem report file.
    I would appreciate some guidance on what I need to do to get this to work.
    Cheers,
    Steve

    We've seen this with a few of our users as well. All started noticing having issues Friday morning. As this is a hosted service for us via webex we had our engineers call in to Jabber support. Cisco performed a modification to their account and they were able to connect again. No SRV records were messed with.
    ***EDIT*** - This appears to have been caused by a certificate issue. The Trusted Root Certificate for QuoVadis expired and was not renewed on some machines. 
    Go here: https://www.quovadisglobal.com/QVRepository/DownloadRootsAndCRL.aspx
    Install the Cert for : QuoVadis Root CA2 (in windows, download as DER>right click file>install)
    Jabber should connect now. The issue was in SSL validation with the appropriate hosted servers.

Maybe you are looking for