10.4.11 Client unable to access 10.6 server

Question

Level 1

8 points

10.4.11 Client unable to access 10.6 server

I have recently setup a Mac Mini 10.6 server and all is working quite nicely with one exception. I have one 10.4.11 client that is unable to access the server. It either doesn't show it under 'My Network' or shows an alias that can't be accessed. Meanwhile, I have two other clients running 10.5.8 that are able to connect without any trouble. Anyone have any ideas? Do I need to do something different to the 10.4 client as I didn't need to do anything for the 10.5 clients. Thanks!

Dual 1.25 GHz PowerPc G4, Dual 2GHz PowerPc G5, Laptop 1.67 GHz PowerPC G4, Mac OS X (10.5.8)

Posted on Jan 20, 2010 10:54 AM

Reply

Answer 1

davidh

Level 4

1,896 points

Jan 20, 2010 1:12 PM in response to RBC03

Is the intent to "connect" for & via AFP ?

Try using (in the Finder) the Go > Connect to Server... item (command - G shortcut)
and connect using:

afp://fqdn.ofyour.server

or if you absolutely must, instead of the server's DNS name use its IP.

Reply

Answer 2

RBC03 Author

Level 1

8 points

Jan 20, 2010 1:57 PM in response to davidh

Yes. I simply want to be able to easily connect to the file sharing on the server.

I was able to get it to work with the IP address. Is this the only way to connect via 10.4? None of the old versions (10.3 server) or the 10.5 clients have to use this method. You used to be able to go under network > my network and select the server and log in. Under 10.5 it is listed as a shared device. But on 10.4 I have to enter the IP address in this fashion, something seems amiss. Do I have something setup wrong?

Reply

Answer 3

davidh

Level 4

1,896 points

Jan 20, 2010 2:05 PM in response to RBC03

Probably.

10.5 (and 10.6) will default to using Bonjour for locating the server.
10.4 probably does not.

This sounds like a DNS issue in part. Proper DNS lookups (forward and reverse) are a must for OS X Server and this is really fairly standard practice anyway.

Please post the unedited results (run via the Terminal, on the server itself) of:

sudo changeip -checkhostname

Reply

Answer 4

RBC03 Author

Level 1

8 points

Jan 21, 2010 9:12 AM in response to davidh

I think all is good with the DNS, but then again, I'm not an expert on servers. Here's the terminal results:

Last login: Thu Jan 21 11:07:48 on console
$ sudo changeip -checkhostname

Primary address = 192.168.1.10

Current HostName = rbc.private
DNS HostName = rbc.private

The names match. There is nothing to change.
dirserv:success = "success"
$

Reply

Answer 5

Jan 21, 2010 10:36 AM in response to RBC03

do this on the 10.4 client in terminal..

dig -t any rbc.private
and then this.
dig -x 192.168.1.10

what do you get?

Reply

Answer 6

RBC03 Author

Level 1

8 points

Jan 21, 2010 11:01 AM in response to Steve Krawcke

Last login: Wed Jan 20 09:30:52 on console
Welcome to Darwin!
$ dig -t any rbc.private

; <<>> DiG 9.3.6-APPLE-P2 <<>> -t any rbc.private
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12145
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;rbc.private. IN ANY

;; AUTHORITY SECTION:
. 10800 IN SOA A.ROOT-SERVERS.NET. NSTLD.VERISIGN-GRS.COM. 2010012100 1800 900 604800 86400

;; Query time: 21 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 21 12:56:39 2010
;; MSG SIZE rcvd: 104

- And -

$ dig -x 192.168.1.10

; <<>> DiG 9.3.6-APPLE-P2 <<>> -x 192.168.1.10
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20280
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;10.1.168.192.in-addr.arpa. IN PTR

;; Query time: 21 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 21 12:59:48 2010
;; MSG SIZE rcvd: 43

Not sure what all this means...

Message was edited by: RBC03

Reply

Answer 7

davidh

Level 4

1,896 points

Jan 21, 2010 11:11 AM in response to RBC03

It means, from - what we're seeing - that in all probability, your server is answering for itself (for DNS), but your clients are not using it for DNS.

Either that or you have another box serving DNS answering for ".private"

Please do (on the server in the Terminal):

cat /etc/resolv.conf

If it comes back with either 127.0.0.1 or 192.168.1.10

Then please go to your clients - at least the 10.4.11 box to start with, and in System Preferences > Network for the active network connection, under Advanced, DNS
put in your server's IP, ie: 192.168.1.10

And then try connecting from the 10.4.11 box

You can also have that info/setting furnished via DHCP but that is another discussion entirely.

Reply

Answer 8

RBC03 Author

Level 1

8 points

Jan 21, 2010 1:28 PM in response to davidh

Ok, it says on the server terminal that that file is not used by the hostname... but returns 127.0.0.1 as the nameserver.

Now on the 10.4 client there is no 'advanced, DNS'. If I go to configure I have a TCP/IP option I can put it under DNS Server which I tried, not sure if this is what you were telling me to do or not, but I tried it and it did not work. The server isn't even listed as an alias under network this time.

Reply

Answer 9

RBC03 Author

Level 1

8 points

Jan 21, 2010 1:30 PM in response to RBC03

So you mention bonjour earlier. This could be that the 10.4 client uses AppleTalk instead?

Reply

Answer 10

davidh

Level 4

1,896 points

Jan 21, 2010 1:35 PM in response to RBC03

Add 192.168.1.10 on the 10.4.11 client as you did previously, and no, it won't show up under Network right away it'll take QUITE some time before it does, and besides, that "Network" browser was always at best somewhat unreliable/unpredictable under 10.4

You should use the Go menu : Go > Connect to server... (cmd-k keyboard shortcut)
and connect using:

afp://rbc.private

I'll bet it comes up rather quickly with an authentication dialog

If not then use

afp://192.168.1.10

Reply

Answer 11

RBC03 Author

Level 1

8 points

Jan 21, 2010 2:15 PM in response to davidh

It did finally show up under Network, but still as just an alias that doesn't work. If I go to Go > Connect to Server, rbc.private still doesn't work, I get a connection failed, like before. If I use the IP address I'm able to connect, just like we did the first time around.

I never had any real issues with the Network browser on 10.4 for any machines, this is the first, but at that time we were running 10.3 Server, not 10.6.

Reply

Answer 12

Atlas Wu

Level 1

0 points

Mar 4, 2010 3:05 AM in response to RBC03

I think there are some bug with this issue.

I run 10.6 server, and use 10.4 to connect in AFP, if the shared folder named in Chinese, it failured. folder named in english, it working...

Reply