Re: Netware 4, 5, 6 - AFP-Server-Fragen

nug@xxxxxxxxxxxxxx <gabi_foster@xxxxxxx> wrote:

> kannst Du mal andeuten, was Dein Perl-Skript bewirken soll?

Hatte ich doch schon. Das Perl-Script ist nicht von mir, sondern Teil
des Unix-AFP-Servers "Netatalk" und ist eine Art Diagnoseskript. Man
läßt es gegen einen AFP-Server (ASIP/AFPoverIP) laufen und er spuckt
einem auf der Konsole aus, was der Server behauptet zu können.

Das sieht dann für Mac OS X 10.4.2 als Server so [1] oder im Fall von
Helios Ethershare so [2] aus. Mich interessieren dabei v.a. die
AFP-Versionen, die UAMs und die Flags.

> ja und zu den Mac-Clients:
> Ich hatte ewig einen 3.12-Server noch laufen weil die Verbindung mit
> den Macs unkompliziert war, zwischendrin wars komplizierter und jetzt
> mit NativeFileAccess geht es wieder ganz einfach. Also bei Mac-Clients
> ist der Schritt von 3.12 nach 6.5 optimal, alles dazwischen auslassen!

Ich will das nicht betreiben, sondern nur testen. Mein Netware 3.12
bleibt wie es ist.-)

Was ist NativeFileAccess genau? Auf den Novell-Seiten findet man viel
Marketinggeblubber, aber nichts handfestes: Welches Protokoll ist das im
Fall des Macs genau? SMB? AFP? NFS? "Nativ" ist hier relativ, Mac OS X
kann ja alle drei. Ich suche aber ausschließlich AFP-Lösungen.


[1]

---->8---->8----
AFP reply from localhost:548
Flags: 1 Cmd: 3 ID: 57005
Reply: DSIGetStatus
Request ID: 57005
Machine type: Macintosh
AFP versions: AFP3.2,AFP3.1,AFPX03,AFP2.2
UAMs: DHCAST128,DHX2,Cleartxt Passwrd,No User Authent
Flags:
SupportsCopyFile,SupportsChgPwd,SupportsServerMessages,SupportsServerSig
nature,SupportsTCP/IP,SupportsSrvrNotifications,SupportsReconnect,Suppor
tsOpenDirectory,SupportsUTF8Servername,SupportsSuperClient
Server name: Bluebird
Signature:
00 11 24 72 2b 62 00 00 00 06 00 00 06 0e 00 00 ..$r+b..........

Network address: 192.168.92.3:548 (TCP/IP address and port)
Network address: fe80:0005:0000:0000:0211:24ff:fe8c:cc37:548 (IPv6
address + port)
Network address: bluebird.air.bit.netz (DNS address)
UTF8 Servername: Bluebird
---->8---->8----


[2]

---->8---->8----
tk@sushi:~$ asip-status.pl 192.168.71.119
AFP reply from 192.168.71.119:548
Flags: 1 Cmd: 3 ID: 57005
Reply: DSIGetStatus
Request ID: 57005
Machine type: EtherShare
AFP versions: AFPVersion 1.1,AFPVersion 2.0,AFPVersion
2.1,AFP2.2,AFPX03,AFP3.1
UAMs: Cleartxt passwrd,Randnum exchange,2-Way Randnum exchange,DHCAST128
Flags:
SupportsCopyFile,SupportsChgPwd,SupportsServerMessages,SupportsServerSig
nature,SupportsTCP/IP,SupportsSrvrNotifications,SupportsReconnect,Suppor
tsUTF8Servername,SupportsSuperClient
Server name: tux
Signature:
98 70 95 16 00 00 00 00 00 00 00 00 00 00 00 00 .p..............

Network address: 192.168.71.119 (TCP/IP address)
Network address: 201.143 (ddp address)
Network address: 192.168.126.119 (TCP/IP address)
Network address: 212.202.164.88 (TCP/IP address)
UTF8 Servername: pizza-funghi
---->8---->8----


Grüße
Götz
--
http://www.knubbelmac.de/
.

Relevant Pages

  • Re: Error code - 5002
    ... Windows 2003 server by using AFP and I get this error message: ... Unknown user authentication method ... traffic between the client and server). ...
    (comp.sys.mac.misc)
  • Re: Macs getting kicked off Win2k
    ... Windows Server 2003 uses the ... older AFP 2.2 file sharing protocol and Mac OS X uses AFP 3.1. ... Be sure that none of your Mac clients have their Energy Saver settings ... advantage of Access Control Lists (ACLs). ...
    (microsoft.public.win2000.macintosh)
  • Re: Cant connect OSX 10.3 & OS9 clients to same Win2k Share
    ... What about Windows 2003 Server would that help? ... the UAM will only apply to AFP connections that you make. ... Mac OS X's version of SMB will split the Mac ...
    (microsoft.public.win2000.macintosh)
  • sometimes users unable to save - network home folder environment
    ... The server is a G5 w/ 6gb ram, ... While we don't use many other apps other than MS Office apps, ... There is nothing in the system log or the console, and the AFP log has ...
    (microsoft.public.mac.office)
  • Re: mac files names problems
    ... I can connect and move files AFP is the solution! ... little permissions problems but it's nothing important. ... It would appear that you are connecting to the w2k3 Server with ... >> characters but w2003 is not accepting this files because of his names ...
    (microsoft.public.win2000.macintosh)