AFP connection Services for Mac has stopped working

[Karen Bowerman]

Today after a virus attack (some type of gaobot) and updates of Microsoft
patches 841872, 841873, and 842526, Macintosh users (OS 9 and OS X) can
no longer connect to our W2K server running Services for Macintosh using
AFP. They can connect using SMB. Box is W2K Server SP4. I applied the same
security fixes to another box running Services for Macintosh trying to find
the offending patch but I can't get it to break. Now I am thinking that it is
not the security updates but that something else is hosed. Event log says
something like reconstructing the database. Does this mean that the macfile
index is damaged? If this is the case would SMB work and AFP not?

Any helpful hints appreciated.

Thanks Karen
(e-mail address removed)

 

[William Smith]

Today after a virus attack (some type of gaobot) and updates of Microsoft
patches 841872, 841873, and 842526, Macintosh users (OS 9 and OS X) can
no longer connect to our W2K server running Services for Macintosh using
AFP. They can connect using SMB. Box is W2K Server SP4. I applied the same
security fixes to another box running Services for Macintosh trying to find
the offending patch but I can't get it to break. Now I am thinking that it is
not the security updates but that something else is hosed. Event log says
something like reconstructing the database. Does this mean that the macfile
index is damaged? If this is the case would SMB work and AFP not?

Hi Karen!

First, test that anti-virus software on the server is not causing the
problem by temporarily disabling it and trying to connect from a Mac.

If this doesn't work then you may have a corrupt index as you've
indicated. You can rebuild the index by deleting your Mac volumes and
then recreating them. This does not delete files; it only deletes the
share point for your Macs to connect.

Hope this helps! bill

 

[KB]

Problem was with Norton AV CE ver 9. We had to completely uninstall AND
reboot the server to get the connections working again. Removing the
offending piece as referenced at macwindows.com did not fix our problem.
Microsoft is recommending going back to ver 8. They also said that
Symantec is posting something about this.

Karen