scan to smb using Windows Vista Home

[doctech]

Are there any tricks to this? I set it up like I do for XP but it did not work.

[Cipher]

Some helpful info in this post below.

http://www.copytechnet.com/forums/connectivity/7272-scan-file-ricoh-canon-machines.html

[fausto1981]

Here you go buddy,

These devices transmit data using packet fragmentation. If this occurs during Scan to SMB, scanned data will not be accepted by the Vista SMB target client. Vista does not accept fragmented packets.

[Resolution]

There is a free patch released from Microsoft but only by request. Please contact Microsoft Support to obtain the patch discussed in KB Article Number: KB935755
KB935755

Good Luck with that!!!

[jeffreyozz]

I had set up a smb folder when I got my Vista test machine. I had no problems.

[fausto1981]

I had no problems either but maybe they are trying to scan to a Vista home edition.. is it the same OS you tried it on before.

[jeffreyozz]

yes it was home edition. If I remember right I set up the smb the same as I did on my xp machine. No tricks, although the network settings dealing with norton had been previously changed, and maybe you have to set the ip to trusted under norton. I have onecare now, so I cant even go through and try to reduplicate.

[Cipher]

Nortons Internet Security 200x will block NetBIOS traffic by default.
I've even had problems after removing the NetBIOS rule and creating a new rule permitting the traffic for the protocol and I.P range.

McAfee use to be even worst.
Everything would be fine then you would go to scan a file in via SMB and by the time you had walked back to your PC you had a BSOD to deal with.

So you definely need to be aware of these various firewall applications that people run can cause issues.

DaZ recommends Comodo Firewall.
It's completely FREE and works well and does not suck your system resourses dry.
But like most firewalls it blocks NetBIOS traffic by default.

[cmpelser]

For me it was as simple as upgrading the firmware!!!

[oldtech]

What model machine?

[Nitrojunki]

Smb and vista

Did anyone have any luck with this hotfix? When I ran it
It reported that it does not apply to my system.
I am running both 64 bit vista home ult and busness version.
There must be a fix for this somewere.

[kayjaig]

Make sure your folder is fully shared in the network

Make sure your folder is fully shared in the network with your Vista.
You may try to use public folder, and mark it shared fully to the network. path will be like this
\\computer name\public
good luck

[Prodigal Son]

You sure the problem isn't rights? Often the machine must log onto the computer with an account and have write-rights in the folder it's to store the file in. I usually set up "C:\Scans" and give the machine full rights in that folder, then share it like kayjaig says, and put the UNC path (\\computername\foldername) in the address book of the machine, along with the logon username and password for the computer (create a new account or use an existing one, remember the account has to have a password set though).

Depending on the network setup logon criterias may or may not be needed, but for Home edition o/s that doesn't have domain logon support it can be a bit tricky to get it to work without having an account for the machine on the computer. Especially on Vista since it has all these security garbage that really only makes it less useful.

In a domain it's a lot easier, since you just create a new user in the active directory of the domain for the machine, and use that account for all computers. Still only works for computers that are logged onto the domain though, i.e not Home edition.

[Nitrojunki]

Yes, I did check to be sure the rights were correct. You can even log into the folder from another workstation and create files and folders using the same log in information. If I cycle the copier and browes to the folder I can get as far as the machine in the workgroup but when I try to access the shared folder it acts like the authentication is wrong. After that it will not even so much as show you the workgroups anymore.

[Nitrojunki]

I took your advice and tried to use the public folder. I get the same thing. I am using the administators account to access it from the copier. You would think the admin would have rights to the public folder eh? By the way, all firewalls and antivirus is down. Nothing should be blocking this. I can access the folder using another workstation however, using the same account information as the copier.

[Prodigal Son]

I took your advice and tried to use the public folder. I get the same thing. I am using the administators account to access it from the copier. You would think the admin would have rights to the public folder eh? By the way, all firewalls and antivirus is down. Nothing should be blocking this. I can access the folder using another workstation however, using the same account information as the copier.

The admin should be able to access it, yes. I would double-check username and password to begin with, it might be case sensitive so be sure to type it correctly. Firewalls and such shouldn't be a problem unless it's timing out. When the firewall blocks traffic the copier will try again and again until it times out and gives you a message. If it immediatly gives you a message (like within 5 seconds) it should a problem with authentication.

The computers are not logged onto a domain, you're sure? (Onto a server). Could you ask the customer to show you the logon process, from when they start the computer until they're on the desktop? That'll give you an idea if they're logging into some sort of system, could be a Windows-domain or a Netware server. You could also check by right-clicking My Computer (or simply 'Computer' in Vista) and go to the 'Computer Name' tab (here is a guide). If there is a field called 'Domain' then they're part of a domain and then the copier must also be member of that domain for it to work properly, but if the same field says 'Workgroup' then the local computer accounts apply. It's important because if the other computers are members of a domain then they have the trust from the domain controller (server) to access any shared resources in the network (that aren't otherwise locked), but if the copier doesn't have an established trust with the domain controller it can't reach much at all.

If there aren't a domain involved; Is the copier member of the same workgroup as the computer/s? That could explain some things, though I wouldn't place my bets on it.

Other than that I'd check for irregularities within Vista. It's known for it's bugs and "security measures" which I personally just hate, for lack of a better word. If all else fails, disable all security stuff within Vista such as the UAC and file protection system. Google for it if you need the know-how.

I hope this helps!


Edit: I just read the thread again and I see it's a Vista Home computer, right? Home editions don't even have domain logons so that shouldn't even be applicable, but still Maybe somebody could use it some other time.