Re: PC network problem
- From: Bob Harris <nospam.News.Bob@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Mar 2008 23:50:18 GMT
In article <1idp448.1cvwcqyff1cxgN%dempson@xxxxxxxxxxxxx>,
dempson@xxxxxxxxxxxxx (David Empson) wrote:
J.J. O'Shea <try.not.to@xxxxxxxxxxx> wrote:
On Tue, 11 Mar 2008 13:59:24 -0400, nospam wrote
(in article <110320080959242077%nospam@xxxxxxxxxxxxxx>):
In article <0001HW.C3FC319B017BD472F02066D8@xxxxxxxxxxxxxxxxxxxxxx>,
J.J. O'Shea <try.not.to@xxxxxxxxxxx> wrote:
About a year ago I created an applescript so that I could mount the
file server automaticaly on startup. this is the script:
"mount volume "afp://<MyUserName>:<MyMacname>@<ServerIP>/<Folder>""
Okay, you _are_ using AppleTalk to mount that volume. (That's what that
'afp'
is.)
nope. afp means apple filing protocol, which can run over appletalk or
tcp. in fact, afp over appletalk is no longer supported (since tiger).
Most people refer to AFP as if it were AppleTalk. Yes, if it's running
under
TCP it's not AppleTalk anymore, but it's also not anything native to
Windows.
AFP over TCP is supported by Windows NT/2000/XP/2003 Server as a
standard feature.
If files larger than 2 GB can't be copied, it is probably a limitation
of Windows Server's AFP implementation. They must be using an old
version of the protocol (Mac OS 9 era) so it is probably only there as a
legacy feature to allow old Macs to be assimilated into the collective.
That is very likely the problem. The AFP protocol originally only
supported 2GB files. The protocol went though several rev's along
the way to allow things like TCP/IP and larger files, etc... But
it is likely that Microsoft did not incorporate these enhancements.
Going between two Macs running Mac OS X, AFP can certainly handle files
larger than 2 GB. I had no problem copying a file larger than 4 GB using
AFP between two Macs running Mac OS X 10.5.2.
Switching to using SMB will probably fix the problem, as long as Samba
on the Mac can handle files larger than 2 GB.
I agree. It might be best figure out the correct smb://...
connection information using
Finder -> Go -> Connect to Server...
and once you know that you should be all set.
One thing to check for is whether Connect to Server... can
"Browse" and see the Windows share. If it can not, there is a
chance that the Mac is looking on the Wrong Windows Workgroup.
You can check your SMB workgroup by looking in /etc/smb.conf
On Panther and Tiger, you can change your SMB workgroup using
Applications -> Utilities -> Directory Access
SMB/CIFS -> Configure
Or you can encode the Workgroup into the SMB://... string:
SMB addr syntax:
smb://wrkgrp;usrnam:psw@svr/shr
wrkgrp: Workgroup
usrnam: Username
psw: Password
svr: Server NetBIOS name or
domain.name.com or
IP address
shr: Share name
If you don't need wrkgrp, usrname, or psw, you do not need to
include them. Mac OS X should prompt for username and password
when you attempt to connect to the Share.
You should be able to get the SMB info from your Windows admin
dudes, as all of the SMB stuff is "Windows Speak".
Bob Harris
.
- Follow-Ups:
- Re: PC network problem
- From: tacit
- Re: PC network problem
- References:
- PC network problem
- From: Sérgio Duarte
- Re: PC network problem
- From: Jolly Roger
- Re: PC network problem
- From: Sérgio Duarte
- Re: PC network problem
- From: J . J . O'Shea
- Re: PC network problem
- From: Sérgio Duarte
- Re: PC network problem
- From: J . J . O'Shea
- Re: PC network problem
- From: nospam
- Re: PC network problem
- From: J . J . O'Shea
- Re: PC network problem
- From: David Empson
- PC network problem
- Prev by Date: Re: Disk Warrior
- Next by Date: Re: Spotlight doesn't turn up everything it should.
- Previous by thread: Re: PC network problem
- Next by thread: Re: PC network problem
- Index(es):
Relevant Pages
|