Page 1 of 1

Printing issue - DBASE

Posted: 28. Mar 2014, 21:57
by bobwax
I have setup two VirtualBox VM's using ver.4.3.2r90405 with Storagecraft. To keep a client running while his server is restored. It's taking way too long.

One of the servers is Windows Server 2003 32Bit running terminal services for 15 -20 users. The only reason it is being used is to support an old LOB app written in Dbase. Until the server failed it worked well under Hyper-v, but since the changeover printing has become a nightmare.

All printing is done thru "net use" commands initiated when dbase is launched. the command is like "net use lpt1 \\server\printer". All dbase printing is simply text dumps and when users print regular stuff directly from Windows, it works flawlessly. The actual redirection is handled on a user by user basis. Since the changeover printing has been erratic. Some jobs go where they are supposed to, while others may print in an adjacent building or at a location across a VPN. It makes no sense.

Has anyone seen this? I may loose a client.

Re: Printing issue - DBASE

Posted: 29. Mar 2014, 20:32
by socratis
If you don't explain in detail why you think a hardware virtualization software might be responsible for this and not a network configuration, I don't know why you should be looking for an answer in VirtualBox forums.

Re: Printing issue - DBASE

Posted: 30. Mar 2014, 02:14
by bobwax
There is no hardware involved. Originally, both servers were run under Hyper-V. They are temporarily running in Virtual Box until we are ready to re-convert.

Re: Printing issue - DBASE

Posted: 30. Mar 2014, 02:17
by mpack
None of that is relevant to the question you were asked, in fact physical hardware wasn't even mentioned.

You were asked why you're asking about your problem here instead of on a networking or dBASE forum. VirtualBox provides the hardware, i.e. the network card. Protocols passing through that card are not it's concern, far less apps running inside the guest OS. And no claim is made that OS images copied from a different platform will work right away. Different VM platforms can be as different from each other as PCs can be. And the fact that this previously ran on Hyper-v adds to the potential hindrances since the guest could have Hyper-v drivers installed.