Anilrgowda

Question: I have a Lanier LD122 (B&W Multifunction Printer/Copier) that has a scan-to-folder option. Under XP this was easy to set up; Simply share a folder on the network, give guest's permission to modify the contents, than point the Lanier at it and it would all work. But under Vista things seem to have changed.... Help.

I can't kick the feeling that the scanner is trying to access the folder but is being denied access based on privileges or something. For instance, if I try to access the scan folder using a UNC path from an XP machine ie. \\ComputerName\ShareName than I get a username/password dialog box. It doesn't matter what I put in for the username and password I am allowed access to the folder. I am assuming this is because I am authenticating as a guest and I have those permissions to the folder. I think this is where the Lanier is getting stuck. There do not seem to be any configurable options for user/pass on the Lanier.

Here is what I have done:
Configured a shared folder with the following permissions:
- Everyone and guest (user and group) has Full Access Share Permissions
- Everyone and guest (user and group) has Full Access NTFS Permissions.

Modified the Local Security Policy as follows (Local Policies -> Security Options):
- Accounts: Guest account status -> Enabled
- Network Access: Allow anonymous SID / Name translation -> Enabled
- Network Access: Let everyone permissions apply to anonymous users -> Enabled
- Network Access: Shares that can be accessed anonymously -> I entered the share name but I am not sure if I configured this one correctly
- Network Access: Sharing and security model for local accounts -> Changed to Guest Only

Now I know not all of these are a good idea but I am just trying to make it work and I will lock it back down afterwards.

Does anyone have any other ideas?

------------------

Anilrgowda

That is really funny.
You think that Microsoft actually consider other manufacturers inconvenience and that of their customers before producing a poorly tested beta quality OS?
Or that Manufacturers know in advance that MS will change the way that the connections work and will modify predated kit to function with it?
Or that the same Manufacturers will modify the OS on kit that they no longer sell just so it will work with the latest OS?

Not in my 12 years experience of installing and maintaining MFPs and Windows and Unix networks. It is not the way that the world works.

For example. W2003 server demands internal secure channel signing. This breaks SMB scanning from MFPs. These devices do not support SCS for good reasons, the only way to get SMB scanning to work is to disable it.
there is still no fix for this in Vista, released 4 years later, because the default is set for external sources, and the only alternative is to install certificates on every device, which is generally pointless.
Fragmented packets are insecure on the internet, but generally not on internal networks.
Also, MS defaults assume corporate network security admin, fast pc, fast ethernet network, low traffic.
If I refused to change defaults where necessary, half of my MFP customers would be unable to print or scan across the network, and half of the rest would be operating at lower than optimum efficiency.

Lots of pre-Vista hardware and software will not work with Vista without tweaking, and lots of it will never work with Vista.

These machines work perfectly well and securely with Windows, Unix and Mac. If you have to tweak it for Vista, it is because when they were made, Vista did not exist.
End of story, live with it.

------------------