cannot map drives after upgrade to 3.4b

[bhailey]

I have installed 3.4b Community on a new Centos 6.4 64-bit server.  I used the full install (all-inclusive) package.  I am able to access the share via browser but when I try to map it as a network drive I get extremely slow performance.  I can eventually access the share but it is painful.  I am using a dir.root, mysql database and alfresco-global.properties file from an existing 3.2r installation on another server.  In the alfresco.log I see multiple errors saying "Access is Denied".  I added RMI service port definitions and a protocols.rootPath statement in the alfresco-global.properties file (as suggested in one post) but that did not change the behavior. I have also seen references to bugs in 3.4b causing user access issues but they did not seem to pertain to the issue I'm having.  Any ideas?

[mitpatoliya]

Issue seems to be with your content store. Your content store(alf_data space) having permission issue.

[bhailey]

Thanks for the reply.  I checked permissions and they are the same as on the original server.  Also, I would think if it were Unix permissions then it would be yes or no.  In this case, I am able to map the repository but accessing it is painfully slow.

Update:  I'm actually running 3.4c, not 3.4b.  I changed the subject to reflect that.