Hi there Xerox Team and Community!
Can you please help me with this problem, because it's still not working as it should be and I didn't found any solution for this.
Thanks and I'm still waiting for solution!
I've asked our software guys to take a look at this for you, but I have not gotten a response back yet. I have just asked again today and hopefully will get a response. As soon as I do, I will post back to this thread for you.
I haven't forgotten about you.
Here is what is going on and our recommendation:
When the Network Scan Utility loads up, it sends a broadcast out on the network stating that it is running and listening on the correct port. The printer sees this request and responds accordingly, acquiring the list of IDs available. However, the Network Scan Utility does not auto-load at startup on the server, nor is it a Server “Service” that starts with the server. When a user uses RDP into the server, the Network Scan Utility will then load since it is set to startup for users. This loading of the Network Scan Utility is seated in the RDP session, meaning once that user logs out of RDP, that instance of Network Scan Utility is closed out and the link between it and the printer is gone.
Recommendation would be to set the server to load the Network Scan Utility upon boot (with a script, bat file, etc).
The situation you described makes perfect sense only in one situation: if I do Log Off from the remote session (RDP), but i always do disconnect and not log off from the remote session (RDP) of the Server, so the instance of Network Scan Utility never gets to be closed out.
Since the problem still persists, I will wait for another solution from you guys.
P.S. Would not be easier to send us a Xerox consultant to solve the problem. I promise I will share the solution on the forum :)
In order for your Scan ID list to populate, you need to have at least one open session to the server and that session has to be running the Network Scan Utility. If there is no active connection that is running the Network Scan application, the printer will not receive an updated list of Server IDs to scan to. That is why we recommended that you set up a login to a "dummy" account locally via a batch file or a startup script. That way, you'll always have that one open session on the server running the Network Scan Utility.
This workaround you have given me sounds like a great ideea, but I need some further help in order to implement it, so can you please tell me how:
- to create a login to a "dummy" account locally via a batch file or a startup script
- to create the batch file (can you give me a concrete example)
Thanks so much for you help and I'm waiting for your answer. Seems that we're getting close :)