I asked another time before, but i'll keep it shorter this time as i didn't explain it properly last time and got the "wrong" response.

I have a computer dedicated JUST for a print server, with an HP 6110 hooked up via USB and the OS is Win2k3 configured as a print server on a wireless connection, which all work fine (so far:) )

I need to be able to reboot this print server from my laptop, but also be able to log back on remotely as i don't have a keyboard, mouse, monitor, etc hooked up to it.

The only way i can Remote Desktop into it is if i've already logged into the print server itself by hooking up a monitor, mouse, KB, etc and literally walking up to it and doing so. So you basically have to have already logged on in order to establish network connections, policies, etc before Remote Desktop will work i'm gathering???

I tried installing Terminal Services so I can log right in remotely without logging in already with another user, but i still get the 120day license issue. I only install it without the licensing portion, but i still get that 120 day notice.

Should i have this server boot up and log in automatically with my PrintOp userid so that it does log someone in automatically and i can Remote Desktop back in when need be without dragging my monitor and everything else just to log someone back on?????

Any ideas or suggestions?

First off, deinstall Terminal Services. You're only using Remote Desktop, which in 2003 is for Remote Administration, not for thin clients to run their apps on the server.

Couple of things you could try though.

I don't know why it's forcing you to log in at the console. Makes no sense to me.

How long are you waiting until after the server reboots to try rdp'ing into it? I've noticed after a reboot you sometimes have to wait around 5 minutes. If you RDP into it before that time, that particular client machine continues to throw errors it can't connect even when other clients can RDP into the same server.

Set the Terminal Services service within the Services MMC to automatic. You shouldn't have to do this, but it's worth trying.

Also, if all you want is to be able to reboot the server, there is a shutdown command. On your XP machine, type shutdown /? for a list of command line parameters. Basically it's...

shutdown -r -m \\computername

You must run it with a local admin account on the box you're trying to shutdown.

"It happens."

After i reboot i don't wait quite 5 minutes, I'll try waiting a little longer. So with Terminal Services removed and using just Remote Desktop should allow me to modidy print settings etc, good! :)

After I reboot my print server and it sits waiting for a user to enter their logon id, password, and domain, I don't HAVE to be logged in under any ID to Remote Desktop in? The server can still query the Active Directory with no Wireless Connection established? I was under the impression when someone logs on the server the wireless software loads, joining the server to the network and establishing a connection which is now seen over the Lan, allowing me to Remote Desktop in.

Also, this Remoting in i'm doing is ONLY at home on my private LAN. The reasoning for all this is because the locations of my Servers and in multiple locations in my house, which some don't allow the space for a monitor, keyboard, etc to save space.

Just trying to understand the process here.. that's all.

"After I reboot my print server and it sits waiting for a user to enter their logon id, password, and domain, I don't HAVE to be logged in under any ID to Remote Desktop in? The server can still query the Active Directory with no Wireless Connection established?"

As long as it's connected into the network, you're good. RDP should work without anyone logged in interactively.

"I was under the impression when someone logs on the server the wireless software loads, joining the server to the network and establishing a connection which is now seen over the Lan, allowing me to Remote Desktop in."

There's got to be a way to have it auto connect into the wireless network within your wireless config utility.

"If that [soiled bed] sheet is a [holy] manifestation, then I'm working on a miracle in my Jockey's!"

As I'm using Software that came with my NetGear WAG111U USB wireless Adapter, should i switch over to the Windows Wireless Networking so no software has to load?

I'm just not sure if there's a way to get the wireless adapter to load without someone actually logging in first, which kind of defeats my purpose of not having to log someone in directly at the box everytime just to allow Remote Desktop access.

Will Windows talk across to the Wireless AP to authenticate the WEP key without someone logging on?

Any ideas?

Thanks for the help on this BTW!

I don't know about the Netgear utility. As for the Windows Zero Wireless Configurator, I don't have a machine with a wireless card in it to see what options there are at the moment.

"It happens."

So pretty much that's where i'm at... I rebooted my Server, went into my Wireless AP and noticed it was showing the mac address there, BUT the status was OFFLINE.

So somehow/someway i have to get my wireless connection to join the network without actually logging someone on to start up the application.

Can this be done is a script?

Anyone? Anyone?

I'd contact Netgear and see if they have this functionality in their config utility.

"It happens."

Well, the only solution i can come up with is to have the system automatically log on the user with a remote reboot, therefore the Wireless software will automatically load with the user profile to establish a network connection and to allow print functionality (as this is a print server) and for remote administration.

My questions:

1) How do i go about allowing a user i created just for administering this print server to automatically log on without me entering the password etc?

2) Should i just make this user (Called PrintOp) a regular user and any changes that need to be made to the system or printer, i should just Remote Desktop in with an Admin Account?

Anything i've forgotten or suggestion are greatly appreciated :)

thanks again...

1. Autologin.

2. You could login with that PrintOp user with RDP into that session it's already started.

"If that [soiled bed] sheet is a [holy] manifestation, then I'm working on a miracle in my Jockey's!"