Trouble access file share through Alias with new DC

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. "fileserv" name in DNS actually points to another alias which is called "emc-san1"
5. If I try to access files by using \\emc-san1 , shares are accessible and normal.
6. If I try the "net use" cmd, I see that the existing drive mappings to "fileserv" say they are disconnected.
7. 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.

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.

Let me know if you need more detail, but I hope I've giving enough info about this!
Thanks!
jumpassociatesAsked:
Who is Participating?
 
jumpassociatesAuthor Commented:
Contacted EMC and they fixed it
0
 
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Is it working via IP address?

Also how many DNS do you have and what does using "nslookup fileserv" on affected clientds show?
0
 
jumpassociatesAuthor Commented:
Hello...

so just tested...

If I try to connect via IP address, I get the same error.

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)
C:\Users\user>nslookup fileserv
Server:  dc1.mynetwork.net
Address:  192.168.10.1
 
Name:    fileserv.mynetwork.net
Address:  192.168.7.1



Hope that helps!
0
 
jumpassociatesAuthor Commented:
so here's some more info, if it helps in any way...

So 'fileserv' and 'emc-san' point to the same IP of our EMC file shares.
Today, I created a new host record in DNS with the name 'testserv' and pointed it to the IP of the EMC unit.

Tested on an affected client and when we try to \\fileserv or \\testserv or \\ipaddress, we get the same access is denied error on all three.
But if we try \\emc-san, we can access the shares just fine.

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 again!
0
 
jumpassociatesAuthor Commented:
EMC fixed it instead of help from the board.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.