Home › Forums › TWAIN Classic › Scanner detection problem
- This topic has 4 replies, 4 voices, and was last updated 13 years, 1 month ago by gabe.
- AuthorPosts
Hello guys ,
i have developed application which detect scanner and i do some business process now problem is my application can detect network scanner as i use same library which .Net master made ,but what is i want to detect scanner which is in VPN in other country.I am connected to VPN Scanner and install proper driver for scanner as well but my application cant detect that VPN Scanner..What is the problem what else need to detect remote scanner ? please help meI’m not sure about your network, but when I connect via VPN to our office, my computer cannot ‘see’ any of the machines on the local network. They are there, and I can connect to them, but only if I already know their names.
So I think (but I’m not sure) that your VPN is just configured not to tell you everything that your normal network tells you.
When you look in your network neighbourhood after connecting your VPN, do all of the other devices and computers on the VPN show up?
check that the port number through which your app is contacting the remote scanner is opened. If not, contact your VPN admin and ask him to open that port. Hope this helps. A.
Hello thanj you guys for reply
let me clear one thing1. I think when we select source from source dialog box then it will show name of devices right? Those devices can be seen in this box just because of every device has DS file which is stored in XP -> C:WINDOWStwain_32
in that folder there is always .ds file which is responsible to detect scanner right ?m i right ? is it .ds file responsible for detecting scanner?
2.my problem is i am now connected with VPN scanner and install all device driver in my machine ,so now in i could not find ds file for that remote scanner in C:WINDOWStwain_32
i don’t know why this is happen because i have install proper device driver also ..
you are correct in the idea that the dialog displays locally installed drivers. but just because the driver is shown does not in any way mean that the device is available. also depending on where you twain_32.dll is located the .ds may or may not need to be in %windr%twain_32 – for example under terminal services you may have a driver installed under the user profile and then to ‘see’ the .ds you would need to have and load the twain_32.ll in the user’s profile
.
- AuthorPosts