I am having the same problem running across a WAN. Thought it was related to Long Printer Names, but they were changed and I am still getting the error. I can trap the error and RETRY ususally works, but not always. Seems alot of people are having this problem but know one has found a bulletproof solition.

The recipe is alway VFP on NT.