Strange Network visibility problem in shared folder

[TAPtech]

I have a client with a Ricoh all-in-one station. The machine is configured to save scans to a shared folder via SMB on a Windows 7 machine set up as a file server.

The scanner scans to the folder just fine, but from one of the other workstations, nothing new appears in the "scans" folder. If you reboot the server and problem workstation, the file shows up.

Has anyone run into this sort of problem before?

 

[YeOldeStonecat]

This thread seems famliar...like you, or someone else with a danged similar issue..posted about 6 months ago.

Is the server running as DC? So the Ricoh is using it for its DNS?
Are there other workstations on the network that the Ricoh scans to? If so...all good? Or similar issue?

Try disabling SMB2 on the Win 7 rig?

Share and Security permissions are ___? for that \\win7rig\scan folder?

 

[TAPtech]

StoneCat,

If you have a good search string let me know, I would like to review the previous issue- it might have my answer. I did have a post about a CNC machine not reading a share on a WHS box quite some time ago- that machine ran DOS, never did try to disable SMB2.0 as we ended up setting a different share for unrelated issues (ex-employee sort of walked out with the server's hard drive )

The "server" is a Windows 7 Pro box. The workstations are all set to DHCP / DNS from the router. There are only 5 PC's in the company.

There is a username/pass setup on the Ricoh scanner to dump into the shared folder. It does this just fine- if you navigate to the folder on the "server" it shows up right away. I think the problem is communication between the workstation and shared folder and not attributable to the scanner. The "scans" folder is a mapped network drive- I have set this up with the IP of the share computer and set that computer to static IP in an attempt to avoid DNS.

I did find some things online regarding refresh times for the network share- registry entries. I made those adjustments but to no avail. I will try to disable SMB2.0, but if that works, what the heck?

 

[YeOldeStonecat]

Ahh OK peer to peer.
Hmmm.... so whack whack IP address is a good approach, leave out master browser debates and name resolution.
//scratches head.

For giggles what if you add a ScanTo folder to an XP rig as a comparative test?

 

[TAPtech]

I should also note-

The folder appears fine. All of the old files in the folder are there, too. Just not the new one! Once you reboot the two machines, it shows up.

 

[TAPtech]

If I had an XP machine there I would! I think I will try SMB2.0 as you mentioned, then try setting a shared folder on the troubled workstation for the scanner to send files directly to. At least that way she won't need to reboot both computers to get the file. Man, that must be annoying.

 

[SAG]

I remember seeing this happen years ago.
Had something to do with the permissions on the files that were newly created. Only a single client computer could NOT see the newly created files. Change the permissions on the files themselves and then the client computer could see them.
It was one of my techs that worked on it so I am not sure what the final resolution was - just chiming in here letting you know that you are not alone.

 

[TAPtech]

disabled SMB2.0, crossing my fingers. I guess we will find out this week. I checked file permissions, none of the files were user specific, everything seemed normal.

 

[TAPtech]

So far so good. Odd that disabling SMB2 would clear this one up.

 

[TAPtech]

It has been quite some time now and disabling SMB2 was the trick.

Just wanted to keep this updated in case some one searches for it in the future.