We have just replaced 2 x win2000 servers connected via 128kb leased line with 2 x Win2003 (64bit) servers.
We have printers defined from server to server
Server A, 192.168.1.150
Local Printers A1 & A2
Network Printers B1 & B2 (On server B)
Server B 192.168.2.150
Local Printers B1 & B2
Network Printers A1 & A2 (On server A)
A user on server A is using Terminal services to access server B and the software requires to send a print job to a printer on his own server A. This worked perfectly on the windows 2000 setup. What we are finding now is that when the terminal services session is opened initially everthing works perfectly but when left idle for a few minutes (even 1-2 minutes) we get error messages in our software re error accessing printers. If we open the printers folder on server B the printers A1 & A2 have "opening" beside them reather than ready. If we log off and back on again the printing will work again for a short time.
The user is despathing orders in a busy warehouse enviroment so this is very urgent