Idontwantspam

Yah, I've seen that before. Quite odd. And here's the WHOIS lookup if anyone's interested: Registration Service Provided By: Enom, Inc Contact: CustomerSupport@enom.com Visit: www.enom.com Domain name: ofallevil.com Administrative Contact: Whois Privacy Protection Service, Inc. Whois Agent (bjgcysrq@whoisprivacyprotect.com) +1.4252740657 Fax: +1.4256960234 PMB 368, 14150 NE 20th St - F1 C/O ofallevil.com Bellevue, WA 98007 US Technical Contact: Whois Privacy Protection Service, Inc. Whois Agent (bjgcysrq@whoisprivacyprotect.com) +1.4252740657 Fax: +1.4256960234 PMB 368, 14150 NE 20th St - F1 C/O ofallevil.com Bellevue, WA 98007 US Registrant Contact: Whois Privacy Protection Service, Inc. Whois Agent (bjgcysrq@whoisprivacyprotect.com) +1.4252740657 Fax: +1.4256960234 PMB 368, 14150 NE 20th St - F1 C/O ofallevil.com Bellevue, WA 98007 US Status: Locked Name Servers: ns3.temns.com ns4.temns.com Creation date: 05 Jun 2002 23:16:41 Expiration date: 05 Jun 2008 23:16:41 =-=-=-= The data in this whois database is provided to you for information purposes only, that is, to assist you in obtaining information about or related to a domain name registration record. We make this information available "as is," and do not guarantee its accuracy. By submitting a whois query, you agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to: (1) enable high volume, automated, electronic processes that stress or load this whois database system providing you this information; or (2) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone. The compilation, repackaging, dissemination or other use of this data is expressly prohibited without prior written consent from us. We reserve the right to modify these terms at any time. By submitting this query, you agree to abide by these terms. Version 6.3 4/3/2002 Verio Inc. - Growing Your Business, One Click At A Time If it were microsoft's domain, they'd have it registered to themselves. But on the other hand, how would they get an exact mirror of the MS site if they didn't have some sort of access to MS's servers.

You're using windows server and you don't know what a domain is? Why are you using a server OS in a home setting to begin with? It seems like overkill and a waste of your money, considering how much server editions cost. Besides, I'd recommend you use the classic logon interface anyways, since it's much more secure. And IMO it looks better, too. As for hacks, you'll have to google them. The only way I know of would be against forum rules to tell you. Sorry.

Umm.... do you have 10 computers? If so, you may want to consider a domain. Also keep in mind that a computer running XP pro or MCE can have a max of 10 connections at once, this means any computers it connects to to access shares or any shares being accessed on it. XP home only gets 5. So be warned. Anyhow, to answer your question: You can have whatever users on one computer, and from any other computer on the network, you can log in as any user on that other machine and access the 1st computer over the network as a user on the computer being accessed over the network. Get it? They can log in to any account on the other PC and still access their own account on the sharing PC. If the account on the PC accessing the share has the same username and password as any account on the sharing PC, then it will assume that it should log in as that user. At some point i'll make a diagrammy sort of thing to better explain it, but not right now. On a sort-of side note: Vista. I have been experimenting with vista lately () and it appears that if you just right-click a folder, choose the sharing tab, then click like advanced sharing or something, that you'll get the same exact dialog as you do in xp when you click sharing. You don't appear to need to turn on or off any settings; that's the default behavior. This was tested on home premium, I assume the same applies to other versions as well.

If Win2K3 is being used in a domain setting, then very no. If it's not, then just regular no. There are hacks out there to enable the welcome screen in win2k3, but you don't want/need to.

Well, I have decided to try dvorak. I was talked into it. I'll report back on my experience.

No, not really. If you click "Add", then "Advanced" then "Find Now" it'll give you a list of all the accounts on the computer, and all the groups, including built-in groups, such as Authenticated Users. If you give permissions to "Authenticated Users" then anyone who has a user account on that PC can view it - when they type in the PC's computer name, they will get a username/password dialog. Any enabled user account on the computer may get in with their username and password. IF the account on the machine sharing the files and the account accessing the files have the same password and username, no prompt will be given, and it will log in as that user. E.g: my name is "bob". I have two computers, computer1 and computer2. On computer1 i have an account called "Bob" with the password "123". On computer2 I have an account called "Bob" and the password "123". If while on computer2, I open \\computer1, i will see any shares on computer1 that Bob has access to. But if my friend "Joe" has an account on computer1 but is using the guest account on computer2, then he will be prompted for a username and password, which he can then enter and get files from computer1. Well, there are two levels of "disabled". There is disabled and then there is cannot-log-in-locally. When you "disable" the guest account in the control panel, it is not really disabled, it just can't log in locally. It can still log in over the network. If it were actually disabled, which has to be done through lusrmgr.msc, then it can't log in over the network at all. Yes, there needs to actually be an account on the machine that is sharing. Share permissions are based of of windows accounts. So if you click add and type "walter" but there is no "walter" account, then you can't log in across the network as "walter" because there IS no "walter". yah? If you want, PM me and I can maybe try to help you over remote assistance.

Well, you sort of have it. First of all, avoid "deny" permissions as much as possible, since they over-ride "allow" permissions. Secondly, keep in mind that users authenticating across the network must have a password - passwordless network logons are not permitted. You do NOT need to have the same user accounts on each PC, although you may if you want to. Any user account on the computer that has the shared files on it will do, as long as it has a password. As I said earlier, they will only see shares you have given them access to. Avoid using "everyone". Just remove it completely from the permissions list. Instead, if you want any logged in user to be able to see a certain share, use the "Authenticated Users" group, which is any user which has provided a valid username and password. If somebody doesn't have an account, they could use the guest account. You will need to give the guest account a password of course for this to work. Also, remember that even if you disable the guest account in the user control panel, you it can still log in across the network. If you have any more questions, feel free to post them!

First off, which version of Windows XP are you using? If it's XP Home, you're out of luck. If it's XP Pro or Media Center, then go open My computer, click Tools > Folder options. Click on the view tab. Uncheck "Use simple file sharing". Now, go to the folder you want to share. Right-click it and choose properties. Go to the sharing tab. Give it a share name. Remember that if you want it to be a hidden share, you can add a $ to the end of the name and it'll be hidden. Now, go click on "permissions". Add/remove users as necessary, and change their rights (view/modify/both) as you wish. Now click ok. When you type in the computer name across the network (i.e. \\computername\sharename) it should prompt for a username and password. These are accounts on the computer that has the shares on it. The user will see whatever shares they have permission to access. As far as vista, no idea, but it might be similar. Perhaps? Oh and for local folders: no way to set passwords, however, you can set permissions on folders so only certain user accounts can access them. After turning off simple file sharing as stated above, right-click a folder, choose properties. Go to the security tab. Edit permissions as needed. Click OK a couple times. Voila.

You can use scheduled tasks, which is a service built in to windows, to have the computer run "shutdown.exe -s -t (however many seconds to show warning for) -c "Any comments"" everyday at whatever time you want.

WHY on earth do you have two windows installs on one partition? I think a clean reinstall, making two separate partitions this time, would make sense.

Looks nice, but... why did you post it here? cough, cough Welcome to MSFN by the way!

This being in the XP forum and all, I'd recommend you put those in a separate topic in the Vista area.

PM a moderator and request that they remove this post. And welcome to MSFN, btw.

Sad? Perhaps. Hilarious? Yes. Perfectly normal and exactly the same as what many people do? DEFINITELY. -looks at clock- -it's 11:40PM-

Wow, you're making good progress! I can't wait to see the finished design. I like the contrast between the former front door and the new one. When do we get to see some pics of the computers?

To all you advising using gpedit: while it's a powerful tool, it unfortunately is a pain in the butt to use in a non-AD environment. Since changes made in gpedit affect all users of that computer, then anything you do to restrict them will restrict you all. You can still do it through the registry, but using gpedit doesn't always work for situations like these. Fortunately, Vista has the ability to apply policies to individual users even in a non-AD environment. However, I personally don't think that outweighs the downsides of moving to vista.

Ooh! Pretty! Yeah, more colors would make it even better. But these sure are awesome....

Heh. sorry. %windir% is an environment variable that automatically expands itself to your windows directory. I usually say %windir% instead of C:\WINDOWS, since not everyone has windows installed on their C: drive, and since some people install it to something other than \WINDOWS. Some other environment variables you may want to know: So yes, it goes in C:\WINDOWS\system32 yes, 24-bit bitmap. As for msgina.dll... you could just replace it, however, I would recommend instead naming it mygina.dll or something else other than msgina.dll. Put it in system32, then open the registry editor and go to HKLM\Software\Microsoft\Windows NT\currentversion\winlogon, and create a new string value named ginaDLL. then change it's value to be the name of said dll. This way, the custom gina will load normally, but in safe mode, it will default to msgina.dll, so if you mess up the custom gina you can just go back and remove the registry key, and all's back to normal. Two notes on this method: one, it won't work if you want to use the welcome screen, but you're smart enough to use classic logon, so it won't matter for you. two, spybot freaks out when you change the ginadll key. You can ignore that. Hope this helps. P.S: a quick note on screenshots: always use the PNG file format for screenshots if at all possible. It's got the best compression, and it isn't lossy like gif and jpeg are.

Heh. This was the exact question that I first asked on this forum. Just replace the images in winbrand.dll, then save the new winbrand.dll to your desktop or whatever. Then boot into safe mode, copy the new winbrand.dll to %windir%\system32, yes you want to replace, then reboot and there it should be. You might want to back up the original winbrand.dll first, and keep it on a floppy or something so that if the new version bombs, you can replace the it with the original. Welcome to MSFN!

OK, not totally sure what you mean, but again, see the link in my sig, it has all the details you need to apply the policies. As for templates... not really. You just kind of have to look around and see what you want to do. Some time (if I have time) I can make a list of "suggested restrictions" or something like that. Registry template? Again, not really, but in the post linked to from my sig it links to an excel doc with all the policy registry settings. e-book? Not that I know of guides: see link in sig. Or just google it, there's info all over the web, mine's just the best. website: Again, google it. or just check out the thing i wrote. Also, for log on hours: net user USERNAME /times:{times | all} Is the logon hours. The times option is expressed as day[-day][,day[-day]],time[-time][,time [-time]], and is limited to 1-hour increments. Days can be spelled out or abbreviated. Hours can be 12-hour or 24-hour notation. For 12-hour notation, use am, pm, a.m., or p.m. The all option specifies that a user can always log on, and a blank value specifies that a user can never log on. Separate day and time entries with a comma, and separate multiple day and time entries with a semicolon.

regedit and regedt32 are the same in xp. Both ought to be there, but regedt32 just opens regedit anyways.

Can you let us know what version of XP you are using? You should start off by making his account be non-administrative. Then, check out the link in my sig for group policies via the registry, and see if that'll work for you. Welcome to MSFN by the way!

o_O Um. are you sure you're up to this? A domain is an alphanumeric name to represent an IP address: for example, the domain of this site is msfn.org. In the sense I was using it, a domain would mean computers grouped together and attached to the same domain, for example, computers.mynet.com. A windows server domain means you have a domain controller that all the computers have an account on, and the users log in to the domain controller through the workstations. Google around a bit to understand. I take it you're NOT on a domain if you don't know what one is. Mods, can this be moved to XP please? Anyhow, users: I'd say, you may want to create an unattended install to use on all the machines. TONS of info on that here. If this is too complicated, then you can use the NET USER command in windows xp to set login hours. Also, for an internet cafe/classroom, I'd suggest using either deepfreeze or windows SteadyState. they let you set an image for the PC that it will reset to every time you reboot, so if customers mess things up, it'll all be back to normal at a reboot. SteadyState, which is free, can also be used to apply some basic group policies to restrict users, as well as other things.

Is this a request? If so, then it's in the wrong forum, since this area is for sharing tips, not requesting them. This topic would be better in the forum dedicated to the specific OS, presumably Windows XP? Assuming windows XP: Are you in a domain environment? If not, then the procedure will be different from if the answer is yes. So give us more info and we'd be glad to try to help you.

Dang! That's good, especially with 0 mistakes!!