Cannot access CIFS shares after installing 2008R2 server.

I've deployed a new Windows 2008R2 server in an existing domain with 2 other non-R2 2008 DCs, but my users are having trouble accessing a the EMC fileshare when they are connected to this new server. They cannot access other non EMC shares just fine.

Does anyone have any ideas on what could be wrong?

Here are some details:

1. New server has roles of DNS, DHCP and AD and looks successful from DNS test and from replication of DHCP and AD from other servers.

2. Our celerra file share is named "fileserv" and when users tried to access it through existing drive mapping, they get prompted for Windows Credentials and says "Access is Denied".

3. If I try to access by running \\fileserv, they get the same error.

4. ping tests to fileserv and ip address are successful.

5. If I try to access by running \\ipaddress, they get the same error.

6. "fileserv" name in DNS actually points to same ip address as "emc-san1" (another alias)

7. If I try to access files by using \\emc-san1 , shares ARE accessible and normal.

8. If I try the "net use" cmd, I see that the existing drive mappings to "fileserv" say they are Unavailable.

8. We have load balancing dhcp servers and only users connected to this dhcp server (the new R2 server) are getting this error. Users still connected to the older non-r2 servers are connecting just fine.

9. I even just tried creating a new DNS record called "testserv" and tried to access file shares via \\testserv and get the same error.

10. Just ungraded the software on the celerra from 5.6.47 to 6 and I'm still getting this issue.

11. We have a printer here that has the Scan to File option where it will scan a document and upload it our fileserver while connecting to it via SMB. This feature no longer works after introducing this R2 server into our domain.

12. It's bugging me because ONLY access to the EMC is wonky. All non EMC shares work fine. If I reboot the R2 server, affected users will work for a little while, but then some users can't connect anymore. It almost seems like it is intermittent, or there is a connection limit and then blocks more users.

For the current workaround, I'm remapping to the "emc-san1" for my users to access files.

Note: I still want my users to ultimately connect to fileserv instead of emc-san1 because we might be removing the emc san soon and I can point "fileserv" to the new storage device.

Any ideas on this?