Tiger Clients

Anyone know if Snow Leopard Server has any issues authenticating Tiger clients?

I keep getting an "unexpected error while binding" when I try to bind my 10.4.11 clients to my OD.
My 10.5 server was fine.

Similar Messages

Mail 2.0.5 CRASHES ON OPEN after Security Update 2005-009(Tiger Client)

I'm trying to figure out how to fix this.
I rebooted into a techtool pro e-drive and repaired permissions (as well as some other repairs to the drive, etc), but it still is crashing.
I created a new user and opened mail just fine there.
So... it is something in my account. Not sure exactly what to do next?

I'm having the same exact problem. (See Mail 2.0.5 crashes when I get new mail). I deleted my preferences & my junk mail settings, to no avail.
A remarkable number of other people are posting with similar problems, just in the past week or so alone, and as far as I can tell, no one has figured it out. There is definitely a bug here. I have a hunch that it may be related to a recent software update. I'm going to post this to the other threads in hopes of garnering some attention from Apple.
For posterity's sake, I am connecting to a Gmail account, a POP account, and a .Mac account.
See also:
Mail keeps crashing
mail 2.0.5 CRASHES ON OPEN after Security Update 2005-009(Tiger Client)
Mail crashes immediately after opening--why?
Mail Crashes CONSTANTLY!
Mail quits when launching
Mail crashes at open
Mail crashes when downloading new mail.

Samba on Linux with Tiger clients

Maybe someone can help me with this, I am not sure if this is the place to ask or not... I have a new Linux (SuSE 10) server running Samba. My issues are two-fold. My Tiger clients have to authenticate manually -twice in order to be able to log in. Second, and this is more important, I cannot write to the Home directory once connected, I get a message saying I do not have permission whenever I try to transfer files. Has anyone seen this? Permissions are set to Read/Write on the Linux box. Any help would be appreciated!

It was answeres in the Networking forum.

Tiger clients having difficulties accessing Snow Leopard update server

Greetings! I have about 500 Macs in my network, running Tiger, Leopard, and Snow Leopard. I just installed a transparent Snow Leopard (Mac mini, 10.6.7) software update server. The update server sits within my network, with my internal DNS server directing all requests to it. The update server uses an external DNS server, so it is able to access the Apple server without any issues and download the updates. Leopard and Snow Leopard clients are able to access it with no issues and download updates.
My Tiger clients, however, are not. When a Tiger client tries to access the update server through Software Update, it displays the message "A networking error has occurred: Error NSURLErrorDomain - 1100 (-1100). Make sure you can connect to the Internet, then try again." I tested this on about a half dozen Macs on different VLANs, including one set up on the same VLAN as the server. Several things: 1) the Tiger clients CAN access the network, network resources, and browse to the software update server's index.sucatalog file using a browser; and 2) the update server has no log entry indicating a connection was attempted by the Tiger client. (It does, however, show plenty of activity by Leopard and Snow Leopard clients.)
If I enter the following command on one of my Tiger clients, it CAN access the update server:
defaults write /Library/Preferences/com.apple.SoftwareUpdate CatalogURL "http://swscan.apple.com:8088/index.sucatalog"
And the update server posts a log entry acknowledging the access. However, I get a message on the client that the software is up to date. The software is not. I tried to update a PowerPC G4 with a fresh installation of 10.4, and I KNOW it needs updating! I copied and enabled all update packages to my server, and I have seen the necessary updates in the list. My clients are unmanaged.
So, after a morning of testing, trial, error, and digging around log files, I've concluded the following:
1. My software update server is not automatically redirecting Tiger clients appropriately (the network error message)
2. The server's index.sucatalog either does not contain the updates list for Tiger clients, or the Tiger clients are not processing it correctly.
So, my questions are, what do I need to do on my server to redirect the Tiger clients appropriately (because it totally defeats the whole purpose of networking to touch every client and change the software updates .plist file), and what file do Tiger clients need to be directed to to get the appropriate updates list? I've looked at the swupd.conf file; it does not have a redirect for Tiger clients, so I added one (directing it to index.sucatalog), but it did not make any difference.
At this point, I am perplexed. Does anyone have any suggestions? I have read the Mac OS X Server System Imaging & Software Update Administration Version 10.6 Snow Leopard manual, and it was not helpful. I've also searched extensively on Google and found little helpful information.
Thank you for any assistance you can provide.

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.

AFP securely from Tiger client to Leopard X Server

I originally posted this just after New Years. I'm hoping now that more people are back from vacation that I can get an answer. Please help!
We recently upgraded our X Server to Leopard. We can't seem to determine how to transfer files securely over AFP from a Tiger client machine to the X Server. Has anyone figured out how to do this?

I suggest posting to the Server Products forums.

Can Leopard Server update Tiger clients?

Can anyone tell me if Leopard server can update the OS of Tiger clients? I know Tiger server can't update Leopard clients, but the other way around?

Hi
Not true. I have a 10.4 OD Master with a managed group using the SUS Service on a 10.5 Server. The 10.5 Server is connected to the 10.4 Directory. DNS Services for both servers are on the 10.4 Server as is the DHCP Service. 10.4 and 10.5 Clients that bind to the 10.4 Server are updated using the 10.5 SUS with no problems at all. The only issue I've seen is 10.5 clients occasionally can't use the 10.5.2 Combo Update on the SUS Server. There is the 'cant expand package properly' error message. At first I thought this was because the latest Intel iMacs were able to update but not Leopard installed PPC models. One solution was to keep a manually downloaded .dmg of the 10.5.2 update on the Server and push it out using ARD or copying it locally and installing it that way. However earlier Intel models - occasionally - are also not updating - pre-dominantly first generation macbooks and macminis but every now and again some of the later Aluminium model iMacs.
This is an intermittent problem though and may be due to the small bandwidth that the SUS server is having to use to access apple's downloads server (1MB). When the SUS was on the 10.4 Server with a higher bandwidth connection (4-5MB) there was never any problems with the downloads but quite a few with the Service stopping itself and having to be restarted using the command line.
The amount downloaded for 10.5 SUS is greater (approx 13-16GB) than 10.4 SUS (approx 10-11GB) - obviously. It took 4-5 days for the 10.5 SUS to make available all the downloaded updates - obviously due to the 1MB connection but also there were problems with accessing the updates server at that time. I think this was because Leopard Server had not long been made available and like a lot others it was in a testing environment where all the services were being tried to see what was worked and what did not.
Tony

Command to Start/Stop "Windows File Sharing" on OsX Tiger Client

Dear Mac Gurus:
How to use command to start/stop “Windows File Sharing” on OSX Tiger client?
Thanks!
Max

Hi Max,
Windows file sharing requires two daemons, nmbd and smbd. They can be started/stopped as follows:
To start (type the following all in a single line):
sudo launchctl load -w /System/Library/LaunchDaemons/nmbd.plist /System/Library/LaunchDaemons/smbd.plist
To stop:
sudo launchctl unload -w /System/Library/LaunchDaemons/nmbd.plist /System/Library/LaunchDaemons/smbd.plist
The option "-w" indicates that the default setting (whether start them at boot time or not) is also modified (the same effect as you turn them on/off via System Preferences -> Sharing). This means, if you start them and shutdown your Mac without stopping them, then they will be automatically restarted next time you reboot the Mac.
If you use "load -F" instead of "laod -w", then they are started but the default setting is not modified (if it is off then remains off).
If you use "unload" instead of "unload -w", then they are stopped the default setting is not modified (if it is on then remains on and will be started at next reboot).
If you feel the commands are too long to type, then you can devide them into two commands, for example:
sudo launchctl load -w /System/Library/LaunchDaemons/nmbd.plist
sudo launchctl load -w /System/Library/LaunchDaemons/smbd.plist
See launchctl man page for more detail.
HTH
PowerMacG4, PowerBookG4, iMac(C2D) Mac OS X (10.4.9)

Tiger clients on a Panther server ?

Can Panther Server serves Tiger clients ?

There were some ldap schema changes in tiger, but those were added in the 10.3.9 server update. Tiger server is, of course, more featureful.

Leopard server, Tiger clients, 'IP address in use' error messages

I am really at my wit's end here. We have about 100 iBooks running 10.4.11 and a couple hundred MacBooks running Leopard. I took away the job of DHCP from my Windows Server 2003 servers because it couldn't seem to keep the Tiger clients straight, and now the Leopard server is doing the same thing. The laptops are shut down and booted often 10 times a day for use in different classes by different students in different segments of the building, but all the same subnet. Very often, iBooks get an "IP in use by [some other Mac's MAC address], server [IP address of Xserve]" it looks just like this: http://podfeet.com/NosillaCast/NC2006_05_21/iperror.jpg
In addition, when I go to look up the client list on the Leopard server via Server Admin, it shows several instances of the same computer name, same MAC address, different IP address, as well as same computer name, different MAC address, same IP address, and, of course, same IP address for two or three different computers. This is as bad as, if not worse, than Windows server! But it's only the Tiger clients, and I can easily see the duplications in the list, why can't the server see that and do something about it?
I am going to be moving to SL server, but not soon enough. Apparently, it's much easier to assign static IP assignments in SL server than Leopard server. I need a resolution for this now, though. I have Googled quite a bit, but nothing I've found matches my situation. And it causes chaos. After the students clear away the IP conflict box, they often cannot log in until a local admin logs in and "renews IP address" or they restart and clear the error boxes until it gets an IP address it will accept.
I can paste in some console logs if that would help, but essentially, the client refuses the IP address offered by the server, so that suggests that it arps the address itself and determines it's already in use. This whole system, which should be so intelligent, seems so clueless. Why doesn't the server realize it's giving the same IP to different computers, listing the same computers twice with the same and different IPs, etc.? Why doesn't the laptop keep trying to get an IP address? It's extremely frustrating for teachers and students alike.
I really thought this would get better using Leopard server instead of the Windows server, but it actually seems worse now. I've done tests to see if there is a different DHCP server somewhere, but none ever shows up.
Anyone with insight, I'd appreciate it. Thanks

MrHoffman wrote:
One big 172.16.0.0/12 subnet? Ok. Not my first choice.
It's /16, but still was not my choice either. With about 50 printers and servers with static IPs that would all need the mask changed, I put off clipping the subnet mask since VLANs were in the works anyway.
MrHoffman wrote:
The network traffic for a DHCP lease or a lease renewal is negligible.
Figure a few messages at intervals of half the lease time for each client.
There already appears to be a DHCP failure here.
I tried many different things with the 2003 Servers, usually two at a time handing out IPs (same subnet, different range, i.e. one serving 172.16.2.1-3.254/16 and the other 172.16.4.1-5.254/16), and the iBooks would often sit for minutes without getting an IP at all. I'd have to turn on the Xserve's DHCP server to hand out an additional range in the subnet (172.16.6.1-254/16), and the iBooks would then snap up IPs and authenticate to AD.
MrHoffman wrote:
And as for the weirdness, I'd be wondering if the DHCP traffic is being filtered by some of the devices present in this network; it's very easy to have a DHCP server active on a WiFi device (which is why most larger sites have them all configured as APs) and it's also easily feasible to have a rogue WiFi around.
Thanks, all good ideas, but I don't think the problem here. I have all Airport Extreme base stations in Bridge Mode. I regularly do scans for rogue APs, and the iBooks would not associate to one anyway - they only know the school network and need admin access to change. In fact, so inflexible is Tiger that when I started changing to WPA2 from WPA, same SSID and password, the iBooks would not associate to the WPA2 networks without local admin login and manually choosing the SSID (and the password was still in the keychain and worked). I then brought some iBooks back to an area with just WPA (older firmware on older Airport could not do WPA2) and the iBooks were once again stranded. Leopard laptops moved seamlessly between the same APs.
I've also done some testing for rogue DHCP servers, but nothing was found, and I've not seen any wierd IPs coming up.
MrHoffman wrote:
Subnetting and vlans are options. If this is a decent-sized network, I'd definitely look to subnet it; you're already in line for subnetting now, what with what is probably mixed faculty and student traffic.
The reason that VLANs are on hold was that I told admin that with our limited wireless network (1 SSID, Airport not VLAN-aware), when they were not in an office with their laptops on ethernet, they'd only get Internet through the wireless (which would be on student/teacher VLAN), no access to admin servers or printers. I was surprised at the vociferous response.
MrHoffman wrote:
I'd probably toss a monitor onto different parts of the network - if you've not already tried this - and go hunting for "surprises". (If you're spec'ing out for bids on an upgrade, having packet-monitoring capabilities and rogue detection is really handy. That'll tell you if you have a rogue, or if DHCP traffic is pushing you over the edge.)
I have an old PC catching syslogs and it has Wireshark, but I haven't turned that on in a while. If I have time, I will see if I can capture anything. I did get bids on Cisco and Procurve wireless and network infrastructure upgrades last year, and pretty much got the 'no way, talk to the hand' response (and a few more Apple APs).
MrHoffman wrote:
Go talk to the finance folks and to the school board, and tell them that their servers and their network traffic are all exposed to the students. If they're not running encryption, they're toast. (And they're potentially toast even if they are.) That discussion both for reasons of budget, and to cover you, as this looks to be the textbook network configuration case that eventually "blows up" on the IT staff.
We're a medium-sized independent high school with a strapped budget. I have requested and explained everything, but it hasn't sunk in. Last year, I made everything work. This year, without all the special qos settings and tweaks to the switches I made last year to keep things mostly together, things are much more wonky (I stripped out all the qos settings over the summer while preparing for the VLANs, which I assumed was a no-brainer to happen. Unfortunately, I didn't document the settings before I cleared them, and I can't quite achieve the same balance this year). And, by the way, IT staff is pretty much me.

Using 10.6 NetBoot v1.0 with Tiger client images on PPC tray-loading iMacs

Hi all - I'm a bit confused over some documentation I'm reading. I'm reviewing the "System Imaging and SW Update Admin" guide for Snow Leopard Server (available at http://images.apple.com/server/macosx/docs/SystemImaging_and_SW_Update_Adminv10.6.pdf) and am puzzled on a few things.
We have several older tray-loading iMacs that currently have client images served up from an old Xserve running OS X Server (Tiger). In the first part of the guide, I saw that the Snow Leopard System Image utility would not work for creating images from older PPC-based systems. However, later in the guide it refers to enable NetBoot 1.0 (which can run alongside NetBoot 2.0) for older clients - specifically including the tray-loading iMac.
So my question is, how can I go about retiring the old Xserve and still serve/maintain these Tiger client images on Snow Leopard Server?
Can I simply copy the images to the share point in the new Snow Leopard Server and enable NetBoot 1.0? Would I need to create a new image (using the Snow Leopard Server System Image Utility) that starts from a source Tiger installation disc and then add appropriate software as packages? Or can I simply use those existing images (with what I presume means software cannot be added) and serve them up on Snow Leopard Server?
Basically, I have those tray-loading iMacs running a fairly minimal setup (base operating system, ability to join to our LDAP server, and very lightweight open source programs). As (if) they die, we are replacing them with newer Intel-based systems. Having said that, there are still at least 9 or so of these tray-loading iMacs quietly humming along with no indication of failure in the near future (nice job, Apple). It's not a problem if I cannot add software to the images (as it seems most software would require Leopard anyway) - but I would like to serve these up on the network. Any thoughts/ideas?

You can copy your existing images to the 10.6 server, enable NetBoot 1.0, and they will be served up just fine. The only thing you would need 10.4 server for is to create new images.

Mounting remote AFP volumes on Panther Server from Tiger client.

Has anyone else had this problem....
When connecting to a remote AFP share hosted on a Mac OS X 10.3.9 server I receive a message "Mount Failed, Could not mount volume “sharename.”. This happens when I enter the FQDN followed by the share name, for example "afp://servername.domain.co.uk/sharepoint". The client is part of an Open Directory domain and automounts work fine during boot as the home directory sharepoint works with local and remote homes. I have setup many 10.3.9 servers and have never encountered this issue on a Panther client.
Any help would be much appreciated and its driving me to distraction!
Regards
James.

We are not using the server for users' home directories, but thanks for that tip.
Today we have also started having issues at another site with a 10.3.8 server and Tiger clients. The behavior is a little different: when connecting to the Pather server with Tiger clients using a keychain-saved password, the client machine will freeze and must be rebooted. The server is showing no process crashes. Deleting the keychain and entering the password each time fixes the problem.
At the other site, the server is 10.3.9 and when Tiger clients tried to connect using a keychain password, their machine would get a spinning beach ball, but they could get out of it.

Upgrade from Tiger (client) to Leopard Server

Hi all,
I have a client with an existing dual G5 box they have running Tiger. They use it as a file share primarily but want the extra functionality of the server OS (viz Leopard server). Is there an upgrade path from OS 10.4 client to 10.5 server or is it a backup/format/restore process for the data? Thanks in advance for any replies.
Cheers
Si

Well, I can offer my opinion on best practice, other opinions may vary.
In the past, you have been able to upgrade client versions to server. I believe this creates a new System folder. In any event, the client OS and the server OS are not the same thing with different features, There are some functional differences. So if you plan to use the Mac as a client and a server, I'd really recommend against that. I'd also recommend erasing the HD and installing the Server OS on a clean HD.
Jeff

Tiger client can not mount the chinese named share point

We have a Snow Leopard Server running AFP with some share points.
Other clients include Macs and Windows XP/Vista connecting well, beside a 10.4.11 powerbook,
this Tiger Macs can also connect with the English name share points,
but while mount the Chinese name share points,
It showed the error means can't find the directory.
Is that a bug?

more information:
nidump -r /exports .
"name" = ( "exports" );
CHILDREN = (
"clients" = ( "192.168.0.10" );
"name" = ( "/backup" );
"opts" = ( "" );
showmount -a returns:
Exports list on localhost:
/backup 192.168.0.10

Tiger client cannot bind to 10.6.8 server

When attempting to bind a 10.4.11 client to our 10.6.8 Open Directory server, the DirectoryService process on the client crashes and the bind fails. 10.5.x and 10.6.x clients have no trouble binding and every other element of ldap, kerberos, and password server appear to be working normally.
We're also noticing errors in slapd.log on the server for 10.4 clients that were previously bound, eg...
"SASL [conn=1637825] Failure: no user in database ed-12377" In these cases, the existing bind appears normal in WGM and the client machine is working as expected.
I'm not looking for suggestions as much as I'd like to see if anyone else is able to bind an ancient 10.4.11 (PPC) client to a 10.6.8 server. The answer to this question would simplify our troubleshooting path significantly. Of course, if you know exactly what's going on here, I'm all ears!
Thanks!
-Lyle
From system.log on the Tiger/10.4.11 client:
Jul 12 11:50:44 Ed-13229 launchd: Server 0 in bootstrap 1103 uid 0: "/usr/sbin/DirectoryService"[255]: exited abnormally: Bus error
Jul 12 11:50:44 Ed-13229 DirectoryService[262]: Launched version 2.1 (v353.6)
Jul 12 11:50:44 Ed-13229 crashdump[261]: DirectoryService crashed
Jul 12 11:50:44 Ed-13229 crashdump[261]: crash report written to: /Library/Logs/CrashReporter/DirectoryService.crash.log
The crash.log from the Tiger/10.4.11 client, edited and limited to just the crashed thread:
OS Version:     10.4.11 (Build 8S165)
Report Version: 4
Command: DirectoryService
Path:    /usr/sbin/DirectoryService
Parent: launchd [1]
Thread: 1
Exception: EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 1 Crashed:
0   libSystem.B.dylib                        0x9002e4cc strcasecmp + 84
1   DirectoryService                         0x00078d70 CLDAPv3Plugin::TryPWSPasswordSet(unsigned long, unsigned long, sLDAPContextData*, tDataBuffer*, char const*) + 372
2   DirectoryService                         0x0003a778 CLDAPv3Plugin::DoAuthenticationOnRecordType(sDoDirNodeAuthOnRecordType*, char const*) + 3440
3   DirectoryService                         0x0001563c CLDAPv3Plugin::HandleRequest(void*) + 848
4   DirectoryService                         0x0001818c CLDAPv3Plugin::ProcessRequest(void*) + 328
5   DirectoryService                         0x000032d8 CRequestHandler::HandlePluginCall(sComData**) + 880
6   DirectoryService                         0x00004274 CRequestHandler::HandleRequest(sComData**) + 92
7   DirectoryService                         0x0000d794 CMessaging::SendInlineMessage(unsigned long) + 196
8   DirectoryService                         0x0001fed8 dsDoDirNodeAuthOnRecordType + 716
9   DirectoryService                         0x0007eba0 CLDAPv3Plugin::DoNewServerBind2(sDoPlugInCustomCall*) + 2364
10 DirectoryService                         0x0007e198 CLDAPv3Plugin::DoNewServerBind(sDoPlugInCustomCall*) + 476
11 DirectoryService                         0x0007bad0 CLDAPv3Plugin::DoPlugInCustomCall(sDoPlugInCustomCall*) + 1920
12 DirectoryService                         0x0001566c CLDAPv3Plugin::HandleRequest(void*) + 896
13 DirectoryService                         0x0001818c CLDAPv3Plugin::ProcessRequest(void*) + 328
14 DirectoryService                         0x000032d8 CRequestHandler::HandlePluginCall(sComData**) + 880
15 DirectoryService                         0x00004274 CRequestHandler::HandleRequest(sComData**) + 92
16 DirectoryService                         0x000428e0 dsmig_do_api_call + 312
17 DirectoryService                         0x000889d8 _Xapi_call + 276
18 DirectoryService                         0x00088684 DirectoryServiceMIG_server + 160
19 DirectoryService                         0x0003cab0 dsmig_demux_notify(mach_msg_header_t*, mach_msg_header_t*) + 480
20 libSystem.B.dylib                        0x90108aec mach_msg_server + 520
21 DirectoryService                         0x0003cdb4 CMigHandlerThread::ThreadMain() + 348
22 ...ectoryServiceCore.Framework           0x971ff5f4 DSCThread::Run() + 52
23 ...ectoryServiceCore.Framework           0x971ff348 DSLThread::_RunWrapper(void*) + 96
24 libSystem.B.dylib                        0x9002b908 _pthread_body + 96

Hi mcraig55,
Thanks for the response and suggestion!
I did review the security settings back when this started. After an OD rebuild (export, demote, promote, import) a few months ago, our standard security settings had not been restored. I tried to bind the 10.4 client with clear text allowed on both sides (server and client). Then, re-enabled the disabling of clear text passwords (what it should have been) and tried again with both sides set the same. In all cases I still get an error:
Unexpected error while binding - operation cancelled.
I also used this kb article (http://support.apple.com/kb/TA25124) to try SSL to see if the behavior would be different - no change.
Interestingly, the directory does show the client in the computer list. However, the Directory Access application doesn't "know" it's bound. Even more bizarre, the client is taking the preferences that were set for the workstation by Open Directory (eg. the message we display at the login window).
So, at this point, it seems to be 'working.' My speculation is that Directory Service crashes on the client before it can tell the Directory Access application that the client is bound.
Funky stuff.
Thanks!

Leopard MDC with Tiger Clients?

I'm well aware of the rule which states MDCs should be the same as, or no more than one version ahead of, the cleints.
So far so good.
Does this mean I can update the MDCs to 10.5.1 server whilst leaving clients on 10.4.11 for the time being?
Trying to update the entire system in one go will spoil my Christmas!

It is possible, if you're using the latest version (1.4.2). Won't work with an earlier version.
Read the release notes for 1.4.2 -- it has specific instructions on exactly what configs are supported and how to upgrade to it.

Tiger Clients

Similar Messages

Maybe you are looking for