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 fileshare when they are connected to this new server.
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 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. If I try to access by running \\ipaddress, they get the same error.
5. "fileserv" name in DNS actually points to same address as "emc-san1"
6. If I try to access files by using \\emc-san1 , shares are accessible and normal.
7. If I try the "net use" cmd, I see that the existing drive mappings to "fileserv" say they are disconnected.
8. We have load balancing dhcp servers and only users connected to this dhcp server (the new 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.
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.
Here's some other info if it can help...
We currently have 4 DNS servers listed.
192.168.10.1 (original DNS #1)
192.168.10.2 (original DNS #2, but currently turned OFF)
192.168.10.3 (new DNS #3, 2008 R2 server)
10.50.10.1 (other DNS server in branch office)
Here is my nslookup results. This user was assigned dhcp from DNS server #3)
One other thing, we have a printer here that does Scan to File onto our fileserver, and that connection doesnt usually work, but every so often it will. the connectivity is almost intermittent. does that make any sense? Can some type of conflict be causing this?
Thanks for any ideas!