[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 191
  • Last Modified:

SBS 2003 to SBS 2011 migrating member servers shares not working

I just migrated from SBS 2003 to SBS 2011.  Emails and client connectivity to new server works fine.  I have problems when users want to access a network share from a member server on the domain.  I get a message shared folder is not accessible, you might not have permission to view this resource.  I can access other member servers with no issue as an administrator.  

Any ideas as to why users can't access member servers or shares on them?

I still have a tempDC controller on the network for migration purposes until I can ensure everything works well, I will decommission it after everything is resolved.
0
Mikejett
Asked:
Mikejett
  • 5
  • 4
1 Solution
 
Cris HannaCommented:
You say you have a Temp DC.  This would suggest that you did a "Swing Migration" through SBSMigration.com.  is that correct?
0
 
MikejettAuthor Commented:
Yes, you are correct.  I seem to have resolved the shares on the member servers by by running RSOP.msc to member server and found that domain users were not added in the “Access this computer from the network”

·         I opened GPMC.msc and followed the following steps on primary DC

·         Opened  Administrative tools and go to local security policies and then to local policies to find User Rights Assignment.
At the top of the policies is a listing for "Access this computer from the network" and add domain users

 

·         Ran gpupdate /force on member server and now we were able to access shares from client PC’s

·         Performed the same steps on another member server with same issue and we were able to access shares


The next issue I am trying to address is that I have scanners on the network that for what ever reason, they are unable to send scanned documents via email.  I can ping them successfully, but that is all.  I Also we have a voice server that handles voice mails ( I did the same policy to this machine as mentioned above) that isn't communicating with our IP phone system as well.  Strangely if I reboot this server, shortly after booting it works briefly but then stops communicating with the phone system.   Not sure what is going on.
0
 
MikejettAuthor Commented:
Also, the TempDC is still connect to the domain.  I plan to decommission this tomorrow.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Verify that the NTFS and Share permissions are as expected.

Usually Share = EVERYONE FULL while NTFS will have either Server\Users or Domain\Users or Domain\Domain Users in place with READ (no MOD).
0
 
MikejettAuthor Commented:
What do you believe is happening with devices on the network (scanners, voicemail server, etc) that are not communicating on the network?  There are no shares to the scanners, it just needs an IP (which I can ping to)  and gateway to function.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
We use the following method to get MFPs/Scanners to scan via a relay on Exchange:

http://bit.ly/131bAvL (MPECS Inc. Blog: MFP/Copier To Scan To E-mail Destined To A Companyweb SharePoint Library How To

Instructions are for SBS 08 but are also relevant to SBS 11 Standard.

EDIT: We have a great setup process guide for SBS 11 Standard here too: http://bit.ly/p3YbXO
0
 
MikejettAuthor Commented:
Philip,  still trying to figure this out.  I had added the connector in exchange as you had stated with no luck so far.  We want to send directly to emails not a shared folder.  Still trying to troubleshooting this.  I had setup the scanner with its own mail account in SBS as well.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
The MFP instructions are for creating an anonymous relay in Exchange that is limited to the IP of the MFP/Copier(s). It works. We have this setup deployed on Exchange 07/10/13.
0
 
MikejettAuthor Commented:
Philip,  I could not get our scanners to work solely  based on the instructions you gave.  I had reference this article as well for setting up our scanners.  

http://lhdinger.wordpress.com/2011/03/05/sbs-2011-and-ricoh-printers-actually-exchange-2010-issue/

The only thing this article did not reference was to select the anonymous users permission in the new connector tab which your article did provide.  Once I had done that, everything work just  fine. Overall you were on the right track.  Thank you for your guidance.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Those instructions are wrong. One does not edit the default anything on an SBS setup.

As I said, the MFP instructions have been in use for years now, since Exchange 2007, and have worked flawlessly.

Make sure the MFP/Copier is set to Anonymous with all authentication on SMTP disabled.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now