Go Premium for a chance to win a PS4. Enter to Win

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

Windows Server 2012 Using Hyper-V SMB Scanning issue

I have just established a new network environment for a client using Windows Server 2012 R2.

The current setup is as follows

1 X HP Dl380 G7, 128 GB RAM 8 X 300GB SAS drives
Have installed Windows SErver 2012 R2 withe Hyper-V role as the host.
Have installed 2 Virtual machines. 1 is the domain controller and the other a fileserver
both using 2012 R2.

All works good but we have problem where by none of the printers, all Ricoh mutlifunction machines cannot scan files to the appropriate shares. They just get stuck in the queue with a waiting status.

I have narrowed it down to the fileserver only as I made some test shares on the Hyper-V controller and the Domain controller and I can scan to those shares. For some reason
I cannot scan to any part of that virtual machine. It is split up into a C: drive and a D: drive and both drives are affected.

Here is the weird problem. 1 printer was working but the other 2 weren't. I had to make some adjustments to the network configuration by Teaming the NICS, after a reboot no printers would scan into the shared folders. All folders have permissions to all users the shares are accessible every other way. We can print to the printers okay just the scanning.

I am aware this might be a SMB problem due to the new SMB format, but am puzzled why one was scanning and then not. I just can't seem to fix the issue. i have checked firmware on printer and is up to date. I have narrowed it down to the fileserver only.

Is there anything I am missing or overlooked. Firewall issue ? or something else.
This is really causing me and my client grief.

I would appreciate any assistance.
0
cdsaus
Asked:
cdsaus
  • 2
3 Solutions
 
dalbersonCommented:
If you have multiple NICs (since you mentioned Teaming), you might want to turn off "register dns" for the alternative NICs. If more than one NIC is trying to register it's IP address in DNS as authoritative for that machine name, it can sometimes cause problems.

I might be way off, but that's what popped into my head. Wish you the best.
0
 
Adam BrownSr Solutions ArchitectCommented:
All folders have permissions to all users the shares are accessible every other way

Can you clarify this, please? Do you mean the share permissions are set to allow all users, or the NTFS permissions? Also make sure the check the settings on your printer to figure out which account is being used to access those shares. In order for printers to connect to shares, they have to have an account to connect with. Make sure that account has the ability to Write to those folders through both share and NTFS permissions. Also make sure that account is enabled and that the password hasn't expired.
0
 
cdsausAuthor Commented:
After trying most recommended settings I have gone back to SMB V1 to solve the issue as
we also had XP Clients who had problems as well.

This fixed the issues immediately.

Not a fix but a workaround.
0
 
cdsausAuthor Commented:
This solved my problem due to some printers and old clients using SMB V1. Not a fix but a workaround for the time being.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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