Hudson connectivity issues with security enabled

We ran into issues with Hudson dropping off connections to slaves once security was enabled on the Hudson server.
We took the following steps to reconnect the servers as a Windows service and they have remained connected with no issues so far:
Verify that the node has Hudson Slave installed as a service. If not, or if the validity of the installed one is in question, follow these steps. Otherwise skip to step g:
a. Configure the node as jnlp on the main Hudson server.
b. Login to the slave machine and open a browser
c. Paste the URL from the jnlp configuration into a browser in the node (ex. http://servername/hudson/computer/slavename/slave-agent.jnlp)
d. If the 'Connected' page doesn't come up, you may need to add the URL to the 'Trusted Sites' in IE security configuration
e.The 'Connected' browser window will have a 'File' - 'Install as a Windows Service' option. Choose this.
f. After installed, stop the Hudson Slave service. Change the login to an account with rights to run the slave service
g. Open the hudson-slave.xml in the Hudson home directory on the slave machine, usually someplace like D:\Hudson
h. In the line with the jnlp URL, add the following after the URL: -jnlpCredentials hudsonusername:password (an account they you have configured in your Hudson security setup)
i. In the Hudson UI, change the slave configuration to use Windows service to connect. Enter user with password as the account to connect.
j. Start the Hudson Slave service on the slave and make sure it's set to 'Automatic' for startup