Last Friday our share on the Win2K server got a message
that it had exceeded 65,000 files and folders. We have
cleaned it up since then but the older MAC's still cannot
see the share. I have deleted the share, deleted File
Services for Mac rebooted the server a couple of times
and they still cannot see the share. I have created
shares on other servers as a test and the MAC's are able
to see them just fine. I am going into Chooser and asking
it to connect by IP address and it just times out. The
OS X boxes can see the share without a problem.
Please help.

In article <466701c47336$b7c202f0$(E-Mail Removed)>,
"E. Wayne Miller" <(E-Mail Removed)> wrote:

> Last Friday our share on the Win2K server got a message
> that it had exceeded 65,000 files and folders. We have
> cleaned it up since then but the older MAC's still cannot
> see the share. I have deleted the share, deleted File
> Services for Mac rebooted the server a couple of times
> and they still cannot see the share. I have created
> shares on other servers as a test and the MAC's are able
> to see them just fine. I am going into Chooser and asking
> it to connect by IP address and it just times out. The
> OS X boxes can see the share without a problem.
> Please help.


Are your Mac OS X machines connecting via "afp://" or "smb://"? If SMB
then you're comparing Apples (pardon the pun) to oranges. If neither
your Mac OS 9 and Mac OS X machines connect via AFP then you probably
have a problem with File Services for Macintosh on the server. You can
try uninstalling and reinstalling them to see if that corrects the
problem.

Hope this helps! bill
--
William M. Smith
(Microsoft Interop MVP)

Bill, I think you've got it all wrong - the problem is (look at the
other threads!) that while OS X clients CAN connect to Win2k servers
using afp, OS 9 clients cannot. We need microsoft to actually look at
this, please! It appears to be related to the recent slew of patches,
but I am not sure.
William Smith <(E-Mail Removed)> wrote in message news:<mecklists-(E-Mail Removed)>...
> In article <466701c47336$b7c202f0$(E-Mail Removed)>,
> "E. Wayne Miller" <(E-Mail Removed)> wrote:
>
> > Last Friday our share on the Win2K server got a message
> > that it had exceeded 65,000 files and folders. We have
> > cleaned it up since then but the older MAC's still cannot
> > see the share. I have deleted the share, deleted File
> > Services for Mac rebooted the server a couple of times
> > and they still cannot see the share. I have created
> > shares on other servers as a test and the MAC's are able
> > to see them just fine. I am going into Chooser and asking
> > it to connect by IP address and it just times out. The
> > OS X boxes can see the share without a problem.
> > Please help.
>
>
> Are your Mac OS X machines connecting via "afp://" or "smb://"? If SMB
> then you're comparing Apples (pardon the pun) to oranges. If neither
> your Mac OS 9 and Mac OS X machines connect via AFP then you probably
> have a problem with File Services for Macintosh on the server. You can
> try uninstalling and reinstalling them to see if that corrects the
> problem.
>
> Hope this helps! bill

In article <(E-Mail Removed)>,
(E-Mail Removed) (Althornin) wrote:

> > > cleaned it up since then but the older MAC's still cannot
> > > see the share. I have deleted the share, deleted File

> > Are your Mac OS X machines connecting via "afp://" or "smb://"? If SMB
> > then you're comparing Apples (pardon the pun) to oranges. If neither
> > your Mac OS 9 and Mac OS X machines connect via AFP then you probably
> > have a problem with File Services for Macintosh on the server. You can
> > try uninstalling and reinstalling them to see if that corrects the
> > problem.

> Bill, I think you've got it all wrong - the problem is (look at the
> other threads!) that while OS X clients CAN connect to Win2k servers
> using afp, OS 9 clients cannot. We need microsoft to actually look at
> this, please! It appears to be related to the recent slew of patches,
> but I am not sure.

Although I'm seeing more and more that Mac OS 9 machines are having
problems connecting after the patches you're referring to, I'll still
always ask about file sharing protocols (AFP vs. SMB) first.

Mac OS X has two ways of connecting to a server while Mac OS 9 has only
one. It's important and easy to eliminate the possibility that the Mac
OS X client is using SMB instead of AFP, which can give confusing
results. Knowing that AFP fails for both machines is a good indication
about where the problem lies. If AFP works for one Mac OS but not the
other then this definitely indicates something has been broken on the
server.

Recently, I've also become aware of problems that can be the result of
anti-virus software. This should either be disabled or uninstalled as
part of the troubleshooting process.

bill
--
William M. Smith
(Microsoft Interop MVP)