Haven't had to connect one to a Kyocera yet but I just left an office where the upgraded to win 7 and now their Ricoh can't talk to it with SMB. It looks like Bill shut it up tighter then a frogs butt. Not sure what the resolution will be. My Ricoh tech rep didn't have any answers. We'll see how Kyocera does with it.
Posts: 88 | Location: Anchorage AK USA | Registered: August 12, 2003
Perhaps they allowed us the scan to file utility to prepare for this kind of problem.
I wish they'd make SFU so it could register itself on the copiers - then end users could actually deploy it! (Or at least salesmen and entry level techs!)
"I just left an office where the upgraded to win 7 "
LOL, don't you mean they are beta testing win7? Seems foolish for any actual business to start running an OS that just hit the streets. Even though there is seemingly a warm fuzzy going around.
I'm not sure what level of functionality Win7 has for WSD without a 2008 server.
I was very glad to see a feature I've been asking for since Windows 2000 came out in Windows 7 Professional. Virtualization is integrated - you can download an XP Virtual Hard Drive and run applications that aren't 7/Vista compliant in XP instead. It's very easy to set up (though it could be even easier if they'd package the two downloads into one).
They should have stopped having 32 bit releases and forget about backward compatibility (except through emulation) - then we'd start seeing more improvement...This message has been edited. Last edited by: Scotty,
From what I've seen, 7 isn't that different from Vista. Granted, the home version of Vista has no Administrator, which made SMB a pain, but with the new SFU, there shouldn't be a any issues. I have run into a number of accounts that wanted scanning, but the shared folder aspect of SMB caused their IT staff to have a conniption. Thanks KM for the new SFU, it works, that's all we ask for.
=========================== Think of how stupid the average person is, and realize half of them are stupider than that. - G. Carlin
Recently I had to create an SMB route to Server 2008 and I found that with perfect setting I just could not ever log in!! The external IT blokey promised me that port 139 was open and there was no known other security policies and I should have no probs. However I COULD get into this folder with my own laptop connected on their network with the same user\pass that I was using for SMB. After some head scratching, I thought I knew that file sharing by windows 'explorer' used port 137 (not sure If im right there) and when I changed the port from 139 to 137 on the SMB set up it worked flawlessly and has done ever since!
This is the only server 08 Ive had to do, and am wondering if this 'trick' may apply in Windows 7 also which I havent got a copy of yet.
Comments?........
Regards, Mark
Posts: 153 | Location: Norfolk, England, UK | Registered: July 09, 2004
it worked for me..you just found a gold mine ,this is & internal info that will come out soon!if u do a little reseach on msn site u will find out u r right..knowing what to look for is key..great job ..uk
xploraiswakco writes with the first Microsoft-confirmed Windows 7 zero-day vulnerability, with a demonstration exploit publicly available. The problem is in SMBv2 and SMBv1 and affects Windows 7 and Windows Server 2008 R2, but not Vista, XP, or Windows Server 2003. A maliciously crafted URI could hard-crash affected machines beyond any remedy besides pushing the white button. "Microsoft said it may patch the problem, but didn't spell out a timetable or commit to an out-of-cycle update before the next regularly-scheduled Patch Tuesday of December 8. Instead, the company suggested users block TCP ports 139 and 445 at the firewall." Reader xploraiswakco adds, "As important as this the mentioned article is, it should also be pointed out that any IT staff worth their pay packet should already have port 139 blocked at the firewall, and probably port 445. too
=========================== Think of how stupid the average person is, and realize half of them are stupider than that. - G. Carlin
well.. just left my first win7 install, 3 pc's hooked up to a Km-5050. I have to admit, i like 7's layout, it seems logical. Could not get SMB scanning to work, ended up using the SFU, no problems whatsoever.
=========================== Think of how stupid the average person is, and realize half of them are stupider than that. - G. Carlin
I got the windows 7 home addition and now have ordered the prof series to see if all the Kyocera applications that did not work with the 64 bit operating systems will now work with it since they have the work with xp feature on this and I assume it will allow me to run 32 bit applications. SFU and SMB work fine.
Originally posted by Techboy: I got the windows 7 home addition and now have ordered the prof series to see if all the Kyocera applications that did not work with the 64 bit operating systems will now work with it since they have the work with xp feature on this and I assume it will allow me to run 32 bit applications. SFU and SMB work fine.
I will let you know if this works
XPMode is just an enhanced version of VirtualPC - it's still a pretty clunky. You're really running a separate virtual machine, so integration for just scan to file would be pretty ludicrous. While it will likely work it is not a real solution. It is really just intended to temporarily address compatibility issues of legacy applications. If they need it for something else, sure - go for it. Otherwise you'd be sucking up a chunk of memory and hard drive space just for scan to file to operate. Also, SFU probably can't be configured to save to Terminal Services Host drives, so they'd have to move stuff from guest to host too
Its programs like IBverup that does not work with my 64 bit application of windows. I am willing to give it a try for future reference. I have more and more customers buying 64 bit computers. I figure I need to keep up with the software for work.
Nice concept though.
