Arrow_Runner

Yeah, I probably will use WPA instead of WEP, thanks. Could you walk me through or give me the link to a good tutorial on how to set up the group policy to control access? I've tried several times in the past to do that and it never works so I must be missing something. Also, I know that wireless can be hacked, but the school already has a wireless infrastructure that 99% of laptops are configured to automatically pick up the schools network, and I'm hoping that the wireless adapter's range will be hampered by the fact that it's mounted inside a metal box. So I'm partly just hoping that no one will notice that there is another wireless signal. If they do notice, I'm hoping that the WPA key and VPN-only access will be enough to stop them, but they have to find the server's WiFi IP address first, which I will set to a static 169.254.x.x address, so no easy DHCP numbers for them. I've never dealt with hacking much, so I don't know how easy/hard it is to get around those things.

Yeah, the computer has to be out in the open Thanks for the suggestion though. Any other thoughts?

I am setting up a server to be used in a classroom that has problems with people hacking into machines and changing settings. My solution to this is to install a headless server that can only be configured via terminal services, but I want to deny port 3389 on the LAN NIC interface. I am going to unmount the computer's front USB ports and connect a wireless adapter to them and mount it inside the case, that way no one will know that there is a wireless connection just by looking. The wireless interface will be configured with a static IP, with a WEP password. I plan to use RRAS to deny port 3389 and VPN on the LAN interface and only allow VPN Protocols and ports on the wireless adapter. Once I have VPNed into the wireless adapter, I can then use terminal services to connect to the LAN NIC and configure the server. I have set up a test system in this configuration and it seems to work like I want it. Is there a better approach/tools to set this up? And can someone tell me why port 3389 is available after I've VPN'd into the computer? I have it blocked and it doesn't work unless I'm VPN'd into the server.

I am setting up a server to be used in a classroom that has problems with people hacking into machines and changing settings. My solution to this is to install a headless server that can only be configured via terminal services, but I want to deny port 3389 on the LAN NIC interface. I am going to unmount the computer's front USB ports and connect a wireless adapter to them and mount it inside the case, that way no one will know that there is a wireless connection just by looking. The wireless interface will be configured with a static IP, with a WEP password. I plan to use RRAS to deny port 3389 and VPN on the LAN interface and only allow VPN Protocols and ports on the wireless adapter. Once I have VPNed into the wireless adapter, I can then use terminal services to connect to the LAN NIC and configure the server. I have set up a test system in this configuration and it seems to work like I want it. Is there a better approach/tools to set this up? And can someone tell me why port 3389 is available after I've VPN'd into the computer? I have it blocked and it doesn't work unless I'm VPN'd into the server.

I think that's exactly what I was looking for, thanks.

In my operating systems class at school, I've taken the role as the sysadmin, and after getting things set up ahead of time, I decided to bring up the idea of creating a wireless access point with one of the usb to wifi adapters we have extra. Is that possible to do with windows 2003? After some research, I've only found Linux implementations of the idea.

How can I set so workstations either lock or log off after a period of inactivity?

I posted this on another thread in the Windows 2003 section, but it was suggested that I try to find my answer here.

Thanks. I went to that site shortly before I found this forum, but from what I can tell, that site mainly deals with XP slipstreaming. I want to slipstream 2003 Server drivers and it seams to be different than XP.

I prefer using RIS to do my OS (re)installs. Problem: Win2k3 doesn't come with support for my Nvidia MCP NIC drivers. I can install them later after I have the OS on, but that keeps me from using RIS to do the install. How does one slipstream NIC drivers to Win2k3?

About time I find a computer forum worth joining! Here's to sharing knowledge!