SMB to 2008R2 Server... HEAD SCRATCHER!

[KalEl]

Hi Guys,

I've got a client with a number of MFPs on their network, different manufacturers. I got called in the other day as they have switched from a 2003 server to 2008R2. All the MFP's on the network had stopped Scanning SMB...

When I arrived it turned out to be only one brand that had stopped working and they are rebadged Kyoceras. with all the new details in I was getting an "1103" fail report.

Name: John Smith
Hostname : JOHNSPC
Port : 139
Destination : Data\Share\Scans\test

As soon as I put the same information in to a different departments machine (A Develop/Konica) it went through straight away.

The things I've tried....

Changed the port number to 445. Same problem.
Given the user the network admins credentials so that have full rights. Same problem.
Browsed the network direct from the copier and saved in the address book and it scanned to the root folder (DATA) and not the specific folder I chose it to scan to.

Created a fresh brand new test account and it scanned successfully even though I got a failed connection when testing it through the machines browser page. File however did not turn up in the destination folder required. it turned up in the DATA folder after I searched the file name.

No matter what I try it goes into that DATA file and not the required folder. I would put it down to the share name but it worked fine on the other brands machine using the same method! Has anyone ever had this problem?

Kyocera models are... DCC2930, FS-C8525 and FS-3140+

Any help is appreciated. Cheers.

[KalEl]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

Sorry also forgot to mention that all three machines are on the latest firmware released. Cheers

[copymech]

Google sharing folders on 2008. There are specific steps to share properly. Sorry i cant elaborate more.

[KalEl]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

Thanks Copymech,

Seems all o.k. to me. I can actually use the machines address book function and browse the clients network (from the copiers). Go on the the server and locate the path I want to go to so all the shares are correct. I then save that into the address book.

But it still just puts it in the data file rather than the "test" folder.

Using the same path in the konica it goes to the "test" folder. I'm finding it really strange that one machine can use the network path and another can't. They are both set to use port 139. I did read somewhere that Kyocera's sometimes struggle with 139 so tried 445. Still the same thing happens. I would have thought that if it can't put it in the folder I told it to I would get a failure report rather than it just dumping it where it feels.

I also removed the \data\share part of the path and put in "\scans\test".... It put it in the DATA folder!!! It's driving me mad!

[MFPTech]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

Could you please clarify ...

- What is the model that has stopped working
- Did this model work before
- Did you log onto that model using the web interface and confirm if you have the right host and file path ...

Thanks,

[TheOwl]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

Sounds like the machine is still remembering the old address. I have had that problem on a Konica Minolta previously and it turned out to be the NVRAM as that is where the machine held its scan addresses.

By the way, here is a bit of information on SMB Ports:

Port 139 - When using SMB on port 139, it is a requirement that NetBIOS over TCP/IP is enabled as the communication requires NetBIOS. On Server 2008 and newer, this isn't enabled out of the box which can cause scanning issues. See below to enable NetBIOS over TCP/IP.

Port 445 - SMB is hosted directly over TCP and there is no requirement for NetBIOS over TCP to be enabled. This was introduced with SMB v2 and part of the idea of sending directly through TCP was to cut down the number of commands within the communication from over a hundred down to 19.

Enabling NetBIOS over TCP/IP:

1. Network and Sharing Center
2. Change Adapter Settings
3. Right click you primary NIC
4. Properties
5. TCP/IPv4
6. Properties
7. Advanced
8. WINS
9. Enabled NetBIOS over TCP/IP

[KalEl]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

Hi MFPTech,

Models that have stopped working are:
Utax CDC1930 (re-badged Kyocera 3050ci) (Worked fine on 2003)
Utax 256i (rebadged FS-C8525) (worked fine on 2003)
Utax 5140L (rebadged 3140+) (This one was installed after the server change and has never worked).

The first two previously worked fine on 2003. They have since shifted over to 2008 and its stopped working properly. Prints fine just won't scan correctly. The last was installed last week and it won't scan at all. All has latest firmware last week.

I can browse to each of the machines IP Addresses using the web interface. From the Machines themselves I can browse the customers network and locate to the exact file I want to scan to. Save that path but yet it still scans to the incorrect path.

Also to note, do have... Develop Ineo+203 (Konica) and that is SMB scanning to the network path fine.

Thanks for your time.

Hi TheOwl,

Interesting about the NVRAM. I'll have a look. My only concern is that I have created brand new address book entries and it is still scanning to the wrong location. Thank you for the information regarding the port numbers, I'll get their IT guys to enable NetBios.

Also, the customer is in the finance sector and there network is locked down tight, could this be a factor?

Thanks for your time and info.

Kal.

[emujo]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

Have you tried disabling the Signed Signature Requiements? By default they are undefined, and undefined is not "disabled" to a product that does not have these signatures built in. EMujo

[KalEl]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

Hi Emujo,

Thanks, I've added it to the things to try. booked in and I'll try various things suggested. Hopefully one will work!

Thanks for everyones suggestions. Fingers crossed.

[vamoursly]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

I would take a look at the advanced firewall settings on server, very different from 2003..

[RollingROARANDA]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

Thanks Copymech,

Seems all o.k. to me. I can actually use the machines address book function and browse the clients network (from the copiers). Go on the the server and locate the path I want to go to so all the shares are correct. I then save that into the address book.

But it still just puts it in the data file rather than the "test" folder.

Using the same path in the konica it goes to the "test" folder. I'm finding it really strange that one machine can use the network path and another can't. They are both set to use port 139. I did read somewhere that Kyocera's sometimes struggle with 139 so tried 445. Still the same thing happens. I would have thought that if it can't put it in the folder I told it to I would get a failure report rather than it just dumping it where it feels.

I also removed the \data\share part of the path and put in "\scans\test".... It put it in the DATA folder!!! It's driving me mad!

Did you check the security/ACL/permissions on the folders?

[KalEl]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

Hi Guys,

Thanks for everyones help...

I did check all the permissions. Basically I can't touch the server as its a financial sector and they won't let a third party near it. They were adamant that it was the kit as another MFP would work. It did baffle me how the Kyocera/Utax would scan but then dump it in the root folder and not the specified path.

So I think it must be the way he has shared it. I sent him this info about 10 days ago and not heard a thing back so fingers crossed. I'll put it in here incase it helps anyone else. This is all info gethered by various replies to my threads so thank you everyone that posted!

Of course now that I have posted it here as fixed, I'll get a call saying "Same problem - Isn't Working". Fingers crossed.

[TheOwl]

Re: SMB to 2008R2 Server... HEAD SCRATCHER!

Testing to another share (fresh or otherwise) is always a good idea in these types of scenarios.

I have had a similar issue with some machines not scanning to file correctly. I wasn't allowed to touch the share itself, but I was allowed to create a temporary share on a desktop computer and give the Active Directory username of the scan account rights to the folder. When that worked without a hitch, the IT guys put their heads together and figured out what was going wrong with the server share.