Connection to OSX Server delayed - no auto connect

when I try to connect to my OSX server it takes around one minute before the connection is established . every morning I have to reconnect with the server (no auto connect). the other two MBP in the office with OSX 10.5 are auto connected every time.
MPB OSX 10.6.2
Server OSX Server 10.5.8
connected over ethernet

Under the Apple Menu ->System Preferences ->Network. The left hand column should display known network connections. Click the little plus sign and add the appropriate connection.
For future reference this information is available via the help menu as are directions that might be easier to understand.

Similar Messages

Outlook doesn't want to connect with OSX Server on 2 out of 3 clients

I have three computers on which I have installed Outlook 2011. All three are running Mavericks. On one of them, a MacBook air, I have established an outlook account connecting to my OSX server with no problems. On the other two computers when I set the parameters the same way, I cannot establish an outlook account. When I use Apple Mail on any of the three machines, I am able to establish accounts for iCloud and the OSX server with no problems. Can anyone point me to the source of this problem or a method for trouble shooting it?

Hi tommy-ch,
Apa kabar,
Do visit and post your thread in boot camp discussion:
http://discussions.apple.com/forum.jspa?forumID=1165&start=0
There are more experience user on bootcamp that might gladly help you out.
Good Luck.

Cant connect to OSX server over network in recovery mode

Hi guys.
First of all, thanks for any help you can give me.
I am running osx server on a mavericks mac mini on a home network. Attached to it I have a 1tb hard drive to which all the macs in my house use time machine to back up over my network and they are stored there.
I have just formatted one of my macs and want to restore it from these time machine backups that are on the osx server on my network.
When i enter recovery mode from boot (COMMAND R), it can see the "backups" on networks "Matts-Mac-Mini" but when i then click "CONNECT" it says "Enter your name and password for the server "Matts-Mac-Mini/local" so that Time Machine can access it.
It gives me a box with NAME and PASSWORD and a CONNECT button.
By DEFAULT the "NAME" it starts with is "root".......which I dont understand.
I have tried every single iteration of names and passwords I can think of but it still wont connect, it either shakes the box or gives an error saying "There was a problem connecting to the server "Matts-Mac-mini.local". Check the server name of IP address and then try again".
I have tried the log in details for the osx server, the login details for the mac im trying to connect from, used root as the username, tried capitals, no capitals, spaces no spaces etc. I am at a total loss and about to tear my hair out!!
Is there anyone able to give me any help with this please, I would be SO grateful!
Many thanks,
hardtofin

I think I have isolated the password, with a certain username and password the box never shakes and instead gives the error: "There was a problem connecting to the server "Matts-Mac-mini.local". Check the server name of IP address and then try again".
Are you able to offer any help with this? I dont see why i can't connect to it, if the imac can already see it?
Many thanks again,
hardtofin

Moving a Time Machine backup from a directly connected external disk to that disk on OSX Server

I have an iMac that has been using an external drive for Time Machine (TM) backups since 2013, so there is a lot of history in the backups. I now have a Mac Mini running OS X Server, and would like to transfer the drive to the Mac Mini, but continue to use the drive as the backup disk, that is, doing TM backups via the TM service on the server. However, if I simply stop TM on the iMac, disconnect the drive, connect it to the Mac Mini, tell OS X Server to use the drive as a backup disk, and tell TM on the iMac to use the Server TM service, it seems that a new backup file is started, rather than continuing to use the old one (symptom: when I enter TM on the iMac, I don't see any of the previous incremental backups).
Is there a way to persuade OSX server to continue to use the old backup file, rather than start anew, losing my history?
Both the Mac Mini and the iMac are running Mavericks and the Mac mini is running the latest version of OSX Server.
thanks

What you are attempting is complex, and I am not certain whether it would be successful. I recommend you buy a new drive and start a new backup today, and set the old drive aside.
I have a somewhat different view of the benefits of what you are calling "History". I think that History just adds complexity to the Backup structure that makes it LESS likely you will be able to do a Restore. And Backups are only as good as their ability to do a proper Restore.
Copies of the currently-present files is all that Time Machine promises to keep -- older files that have been removed from the current source are not necessarily maintained on the Backup. In my opinion, a fresh, clean Backup from today is more likely to be able to Restore the things you need most -- without any error messages.
The most requested Restores are things Users broke or discarded today or yesterday, and those will be readily available tomorrow and going forward. In the event you need some really old copies of something, you can try to get them off the old Backup drive you set aside today.

Trouble connecting to OSX server from XP domain members

Can someone help me out with a problem connecting to our OS X server from Windows XP? Basically, I only have trouble connecting from XP machines that are members of the domain.
Here are some details:
OS X Server 10.3.9, bound to domain through Active Directory.
Windows Services role = Domain Member.
Computer name (under Windows Services) = macserver
Connects fine from Macs via Network>Domain>macserver
macserver IP address: 192.168.1.5
Sharing 1 folder to all members of the domain.
I can connect fine from OS X computers and XP computers that are NOT members of the domain
I can connect from XP domain members via the IP address \\192.168.1.5
I cannot connect from XP domain members via Network Neighborhood>Domain>macserver, or by entering the computer name. Error message recieved: "The account is not authorized to log on from this location."
I can ping macserver from any xp machine and it resolves the IP address.
I can browse the webserver on OSX Server via http://macserver.
Any thoughts?
Thanks,
Eric
PowerMac G4, MDD Mac OS X (10.3.9)
PowerMac G4, MDD Mac OS X (10.3.8)

I can't remember how I resolved this. I think I had a number of problems, for instance, spaces in fileshare names. I might also have set up the domain incorrectly. Who knows.

Is it possible to connect my home computer to files stored on my running osx server mac via VPN

Is it possible to connect my home computer to files stored on my running osx server mac via VPN. I have VPN set up and can access the Calendar and Contacts via a web browser, however I want to be able to access data files store on the hard drive and shared external drives connected to it. The MacPro runs OSX Server Lion. Any Ideas if this is even possible or how to do it!

Yeah, that's what I kinda figured. Maybe there is another solution - here is my situation:
I have internet and cable service through Telus. Telus' system consists of a modem/set-top-box that provides internet (ethernet and wifi) and TV signal (corded) for one TV and another set top box that provides internet (ethernet only) and TV signal (corded) for my other TV in the basement.
I have an Airport Extreme connected to the modem upstairs which I am using as my home network wifi. I also have an external hard drive (USB) connected to it on which my iTunes library is shared with all Apple machines in my home network.
My upstairs ATV, connected to my APE, works fine and streams internet (Netflix), iTunes Store and my shared iTunes drive just fine - the APE is 3 feet away with a great signal.
My downstairs ATV, also connected to my APE via wifi, does not stream so well, particularly the media from the shared drive. I suspect that this is the case because of signal degredation.
Any suggestions on how to reconstruct my home network to enable my downstairs ATV to work properly?

Newbie: Connect Windows - OSX Server

Hi
I'm completely new with osx server. Installed it 5 min ago
I'm wondering how i manage to get a remote desktop connection from a windows machine to the osx server?
If i try on the windows the remote desktop with the IP of the server it can't connect.
By the way, how to i manage to get a remote connection from mac to mac server?
Thx

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.

OSX Server connects to router but dos not reach the internet

Sorry that i have no answer, but i'd like to add my problem as well.
I have a OSX Server witch is configured to an Airport Extreme. It is connected to the Router and dos all the sharing on the local network. But same as you describe it dos not connect to the Internet.
I checked my firewall options and it is set to allow all traffic.
I can ping the router but i don't get pings from pages on www !?
If anyone has an Idea where else i might look, i would be grateful for all advice..
Please drop me a mail on tj{at}daemgen.net
If anyone has a solution to the problem i will send an coupon for an Starbucks coffee in addition to my appreciation and thanks as i am looking since quite a while by now and it doesn't seem that i see what might cause the problem !!

There really isn't enough data to answer your question directly, but there are some things to check.
Being able to ping or serve data to the local network just means that the server has a working network connection, so that's a start, but to get to external sites it needs two things - first, a valid DNS server address that it can use to lookup hostnames, and it needs to know the address of the router on the network that provides an internet connection.
In this case you should check System Preferences -> Network -> Ethernet -> Advanced and check the TCP/IP settings - make sure the Router (or 'Gateway') address is set to the address of your Airport Extreme. Then check the DNS setting to make sure you have a valid DNS server set.
If those are correct then you'll need to post back with more data, specifically what you do see/get when you try to access remote sites. What error messages do you get?
Oh, and while ping might be a good basic test, it isn't absolute - in other words, ping could fail, even when you can connect to a remote server, since pings could be blocked by a firewall or router at either end of the network.

IChat LAN-LAN bonjour connection via OSX-Server and Draytek routers ?

We want to configure a LAN-LAN iChat intranet connection via our OSX-Server and several Draytek 2600 routers. We have static IP-addresses in all local LANs, do LAN-connection via DynDNS and opened the iChat NAT-Ports on every router as described in several posts.
LAN-LAN connection (e.g. volume mounting and ARD (Apple Remote Desktop)) works fine. We started iChat on every Mac and chatting via .mac accounts also works, but not via Bonjour. The logged-in users are not listed in the iChat bonjour contact list.
What do we have to configure more ? Starting the iChat service on the OSX-Server ?
Thanks in advance for help
Alex
PowerPC G5 DP 1.8MHz Mac OS X (10.4.9) 1GB RAM 22 Display
PowerPC G5 DP 1.8MHz Mac OS X (10.4.6) 1GB RAM 22 Display
PowerPC G5 DP 1.8MHz Mac OS X (10.4.6) 1GB RAM 22 Display

Bonjour works without a server but will only work within the same subnet. It's likely your routers are on different subnets and so using Bonjour you would only be able to see contacts on the same subnet.
If you're not seeing anybody else at all, even those on the same subnet as you, then perhaps your firewall hasn't been opened to the iChat Bonjour ports (TCP, 5297 and 5298). There's also an entry for it in each Mac's Firewall config pane.
You best bet may be to run an XMPP server. iChat server is an XMPP/Jabber server (using a copy of the pretty old Jabberd 1.4 code), but you might want to consider running the superior OpenFire (http://www.igniterealtime.org/projects/openfire/index.jsp) on your server instead.
Just create all the users on the server and then enter the relevant details into each copy of iChat.

Slow connection to OSX Server 10.6

Running 10.6.5 server on 10.6.5 clients.
Anyone notice how slow it can be to connect when using the shortname for the username?
If you connect using the long name it's instant? Any ideas?
This is file sharing using Open Directory.

I am also finding authenticating against osx server / directory or workgroup manager very slow. When I login to a Network Account it takes several minutes.

Connection reset by peer when trying to update to OSX server 3.01 on 10.9

connection reset by peer when trying to update to OSX server 3.01 on 10.9. PLease help

Assuming your network is working for other activities, and it's just the Mac App Store that's failing...
Try restarting the download within the Mac App Store.
Failing that, restart Mac App Store and try restarting the download again.
Then failing all that, I'd close Mac App Store, reboot the system, and open and try the Mac App Store download again.
Here are some details on the Mac App Store (including how to cancel and restart downloads), and here are the App Store Troubleshooting suggestions from Apple.

SMB connection attempt switches to WebDAV unexpectedly when connecting to OSX server

With Windows 8.1, I can connect to my OSX 10.9.5 Server share point by opening File Explorer, typing: \\<fqdn> and hitting return. I will be prompted for server credentials and when I enter them, I will see the share point.
With Window 10, if I do the same thing, instead of seeing the shareppoint, I see a blank Windows Explorer screen with "This folder is empty".
I contacted Apple with a tcpdump from this and they said that Windows 10 is attempting to connect over HTTP instead of SMB:
ACTION: Windows is handling the connection incorrectly by attempting to use Webdav instead of SMB.
STATUS: As with any other 3rd party integration cases, we attempt to identify an issue as either an issue to a 3rd party product, or to identify and isolate the issue in
the Apple product.
In packet 64 the client sends an SMB 1 negotiate request (expected).  In packet 66 the server responds in SMB 2 with the SMB 2 features it supports
(expected).  In packet 67 the client sends the SMB 2 negotiation request (expected).  In packet 69 the server responds with the SMB2 negotiation response (expected).
Normally at this point the client will send an authentication attempt in SMB 2 using one of the authentication types provided by the server in packets 66 or 69.  Instead
the Windows client sends a tcp connection reset in packet 70 (unexpected).  In packet 74 the windows client initiates a connection over HTTP (extremely unexpected).
The above pattern repeats several times in the tcpdump.
The mac server never presented any HTTP information in the SMB packets.  This appears to be a purely Windows 10 issue.
If I connect to the server by typing: \\<fqdn>\sharepoint -- then I do connect, but the OSX server does not indicate this is an SMB connection, so it must be a WebDav connection (which would be incredibly wrong...)
If this is a settings issue in Windows 10 that is forcing an HTTP connection over an SMB attempt -- can somebody point me where to look?

On Thu, 20 Nov 2014 17:04:11 +0000, steve maser wrote:
According to Apple, it appears that if the SMB server (in this case Mac OS X 10.10.1) has port 443 open, Windows 10 attempts to connect over that instead of over the SMB port.
Anybody looking at this one?
If you want someone to look at this you need to file it using the Feedback
tool, if you haven't already done so.
Paul Adare - FIM CM MVP
Actually, we have scientifically determined that Heisenberg did indeed
sleep exactly here. However, we have no idea whatsoever just how fast
asleep he was. -- Dave Aronson

File locking with OSX Server & Microsoft Word

We have a small office LAN based on a Airport Extreme bases station. Periodically Microsoft Word reports a break in connection to the shared folder where we store documents to get disconnected. When that happens and the user reconnects to the share, the user gets the file read-only message for the Word document that was open at the time.
I have found that in order to clear the read-only flag, I have to restart the server and open the Word file on the server with the ID of the user who was editing the file on the remote computer. Only that seems to clear the file locking that causes the file to be read-only.
I cannot figure out a less drastic way to release the lock file. I don't see any hidden temp files in the same folder as the document that is locked for editing found by ls -a or in the root direction of the shared folder in the .TemporaryItems/folders.<UID> that seems to be holding the lock.
I have run chflags nouchg <Word file> from Terminal, but that seems to have no effect either. I also used xattr to see if there were any locks held that way, but I don't see anything that way either.
File sharing to Macs only, which are configured just to use AFP through OSX Server.
Does anyone understand how the file locks of Word documents can be released directly with out restarting the server?
I should add that the underlying problems seems to be WiFi related. The behavior is that the WiFi connection seems to break long enough that the shared volumes disconnects. Outlook also causes a break. This behavior seems to have started with 10.9 and the purchase of new Retina Display MacBook Pros. I turned off AppNap on the Office applications but that is not clearly helpful. I also have been told the problem seems more likely to occur when Word is open in the background and another program like Outlook is in the foreground.
Any suggestions appreciated.

Apple write an operating system and also produce file sharing software as part of that to be used as a file server. Apple provide documentation for third-party software developers on how they should write software to work with Apple's software and also give those developers early access to new versions so those third-party developers can test and if needed make adjustments and issue updates to cope with any Apple changes.
Some third-party developers are good at dealing with this, some are bad, and some totally ignore what Apple does and give the impression they don't care if their product works properly or not. I think we can all judge where Microsoft sits.
It appears Microsoft have never paid any attention in particular to how Apple expect file-locking to be handled when accessing files on a Mac server. There have been problems for years and years and years with Office. Two other problems I have seen which seem different to yours but probably related are -
With Office documents it is supposed to be possible for more than one person to edit the same file at the same time, consider it a miracle if this actually works
With Office in particular Word, there is an auto-save function, unfortunately the way this seems to be implemented it seems that Word creates a new temporary file each time it auto-saves the document and keeps all the previous temporary files open still, this eventually means potentially over a hundred temporary files are open - just for one Word document and you can then hit a limit on the total number of files you are allowed to have open at the same time. At this point further auto-saves fail, and you also encounter great difficulty doing a real full save of the document.
I do not hold Apple completely blameless over this issue, it is likely their file-locking implementations change too often, and have inadequate documentation, however even considering this a company the size of Microsoft with the amount of sales (and profit) they derive from Office for the Mac has no excuses at all for failing to put the effort in to resolve any such clearly critical problems.
We could go on and on about other areas where Microsoft don't play by the (software) rules. Even in Windows Office does not obey the standard print dialog rules Microsoft specified themselves!
Unfortunately not only is Office for Mac upgraded infrequently, but even when new paid for upgrades are released Microsoft have a history of still not fixing bugs. It goes without saying that a mere free update is even less likely to actually fix a bug, typically such free updates only address security issues. The next version of Office is going to be Office for Mac 2014 see http://www.macworld.com/article/2106643/microsoft-will-release-a-new-version-of- office-for-mac-this-year.html
One area I confidently predict Microsoft not to resolve in Office for Mac 2014 is that fact that Word for Mac still does not support right-to-left languages like Hebrew and Arabic. This is despite the fact that OS X itself has supported this for years and years, and despite the fact other Mac programs support this including the free TextEdit and Pages - both of which can read Word files. Some people may remember that at one point the Israeli Government temporarily banned all Microsoft software over this issue. See http://apple-beta.slashdot.org/story/03/10/15/2215249/israeli-government-suspend s-microsoft-contracts This issue goes back over TEN years!!
I note that Microsoft has now taken their OfficeForMac blog offline, probably due to the weight of criticisms. I would not say it is due to out-right anti-Microsoft hate, that war ended long ago. We just want products that work. I myself do use Microsoft products, even at home - where they are the best solution, so I use Microsoft Media Center for example. Sadly this is now being neglected by Microsoft.

Using Amazon S3 as linked storage with OSX Server 10.6.7

Hello everyone!
I will be getting a nice Mac Mini OSX Server tomorrow. I'm not new to networking and I've done over a month of reading the PDF's here that are related to the server and software. I think it's a great tool at a great price.
My question is:
1) Is there a way I can use the S3 Amazon Simple Storage Service as secured linked storage space or SMB to the OS X Server?
2) Is there a way that the OSX Server software can pass both the S3 Access Key and Secret Key to S3 to securely access directories on the S3 Amazon Cloud?
I would like to use S3 Amazon Simple Storage as a secured disk space solution that would be reliable a quick. Am I asking too much?
Thanks!
JT

Would it be a good idea to have another computer link to the Amazon S3 then have the OSX Server link through that computer to S3?
Or would I have to create a script / CGI to authenticate to Amazon S3 to access the directories.
My goal is to use Amazon S3 as copy and playback storage.Like a hard disk connected to the OSX Server via a firewire or an Ethernet connection. Does the sound too simple? It must be possible.

Can I use my external hdd with OSX server

Hi i am thinking about using OSX server, but I dont have very much space on the computer I would b running it of of so I would store everything on my 4TB Wd external HDD. Is this posible, and how would I set it up to do that? Also, my external also has some backups from other computers on it and will I loose any of that? I would probably partition it so that 1TB of it has all the servers files and everything.
Thanks,
Ben

Yep you can use any connected drive for server storage, its under the settings tab called Service Data
No you wouldn't lose anything on the drive (assuming its Mac formatted) but clean partition would be a good idea

Connection to OSX Server delayed - no auto connect

Similar Messages

Maybe you are looking for