Recent content by jcurtiss

I've set Group policy so that "time limit for disconnected sessions" is 1 minute, "time limit for active but idle sessions" is 1 minute, and "terminate session when time limits are reached" is enabled." i've done a gpupdate and gpresult on a test server, and the policy has been applied...

so i can't load the 2000 server adminpak on an xp client. fine. so i have to load the 2003 server adminpak to administer a 2000 server from an xp client. fine. but they took the IAS snap-in out of the 2003 adminpak. so how can i administer a 2000 IAS server from an xp client?

should i start including the following in a signature so it's in every post? ********************* from my march 23 post: "from my original post, "i can't connect with TS client or xp remote desktop." no host-based firewall anywhere. no dhcp, everything is static. dns is correct, traffic is...

are you using roaming profiles? even if you're not, there is a lot of stuff going on at bootup. sometimes the wireless cards take a minute or two to start up and find your WLAN; much longer than a normal wired NIC. i have to watch the link light on my PC card on my laptop and wait until it stops...

the error message comes up as soon as i click 'connect' on remote desktop. i never see the windows logon screen. as i said, it's the same error message i get when i attempt to connect to a machine that i know is NOT running terminal services. i am a domain admin.

these attempts are not going through a router. they are on the local subnet. but for the record, my linksys box is currently forwarding port 3389 to the ip address of my server; waiting patiently for the day that i can get the server to accept inbound TS connections. the clients have 1 (one) DNS...

except i'm not on a WAN, i'm in a 2 bedroom apartment connecting through a $30 linksys switch, which i'm pretty sure is incapable of blocking telnet. where do i turn off smb signing?

i have attempted this with xp2 remote desktop. i have attempted it with the remote desktop client for 2000 pro, as well as the terminal services client for 2000 pro. this is a domain at my house with one server that is the domain controller and DNS server and TS server. name resolution is not...

what if you try to create and save docs directly on the file server? like load word on there. i had that error message locally today and it was a a bad hard drive issue. run chkdsk on the file server drives.

98 doesn't like 2000 or AD. i think there's even a download available from microsoft to help 98 talk to AD, but i can't remember what it's called. i assume from your verbage that this didn't happen when you were using NT.

you don't have to have AD running on both servers; but you have to set up IAS (windows version of RADIUS), and i believe you have to do it on the domain controller. then the VPN server will take inbound credentials and bounce them off the domain controller.

you can change the name of the local admin account with GP but you can't set the password.

to sync with an external NTP server, from a command line on the domain controller: net time /setsntp:ntp.server.com

from my original post, "i can't connect with TS client or xp remote desktop." the idea behind telnetting is that if TS is running, it has to be listening, and it's supposed to be listening on 3389. if i check services, Terminal Services is running. do a net start from a command line, Terminal...

yes, i can ping it, and i can log onto it (it's the domain controller.) what i can't do is telnet to it on port 3389. which tells me that terminal services isn't REALLY running, even though it says it is in Services. i can telnet to it on port 80, where IIS is running. telnet to is on port 5631...