clutch

Yep. http://www.isaserver.org/

Are you using DHCP for the client? If so, try using a static assignment with the DNS entries pointing to your server. Windows uses "Media Sense" to detect line state, and during the boot process some adapters can be shut down when using DHCP, hence losing connectivity while the system is still negotiating its credentials with the directory.

Video: I dig the newest stuff from ATi, and it's just getting better. They finally got it together, and their drivers have been wonderful with their hardware. Chipset: If going AMD, I would pick nForce or SiS, as I have never had good luck with Via (and neither have my friends). If going Intel, then I would use an Intel chipset (although SiS has had some creative stuff). HDD: I always get WD, but that's just me. DVD Burner: I dig my Sony, but I haven't really paid that much attention to other vendors. Sound: Most onboard sound setups are really quite good now (especially the nForce stuff, if going that route). Unless you are looking for other features (like remote control and breakout box with the Audigy Series, 24bit sound, etc.), I wouldn't bother with anything else. Case: I have a Chieftec case, which is like most of the cases you see these days. It's been great. PSU: While this wasn't mentioned, it should be addressed. My favs have been PC Power and Cooling and Enermax, although I use another one that I can't think of right now.

List error numbers and messages that you are receiving on both the client and server.

I don't have anything on Exchange, but I can tell you that we have AD currently running over VPNs, so the theory is sound. We have a central enclave, with hubsites and local sites that have their own DCs and GC copies. We will be switching out to other secure methods to cut down on the communications cost (as we will have 300-500 DCs in CONUS alone) but the VPN solution has worked fine.

Make sure that you have the client's DNS (and WINS, if appropriate) settings pointing to your DC. Make sure that the client does *not* have any other server's IP setup in its DNS and WINS settings, as this can confuse the workstation when trying to resolve DNS names. Also, make sure that the IP settings on the DC are set to point to itself (DNS and WINS entries, if WINS is being used) and use your ISP's DNS IPs as "Forwarders" for the DNS server. This will permit the DC to resolve outside (Internet and other networks outside) domain names for itself and clients.

Do not spam again.

Quote: Ok go to the domain controller and deleted the computer account. Always join the PC to the domain from the pc itself, XP and Win 2000 joining a domain should be done from the work station there seems to be a bug in a NT 4 server while win 2000 or XP is trying to join by adding the computer name to the PDC then going to the workstation. We run into this all the time at the G.E. site i'm at. Bingo. I stated this once before, and got a pm from someone demanding to know why. I never, ever, ever create a machine account for a PC or member server to join. It's much better to do it from the system. However, Active Directory (Windows 2000/2003) is much better about letting systems join existing accounts than NT ever was. While it can be done in theory, the odds of it working are low with NT. However, while stern was mentioning an issue with joining 2000/XP to in this manner, I have seen it with NT clients as well, hence why I join and create the machine account at the same time from the client.

I don't know how your Forest/domain setup is, but basically you would set it up as in my last post here: http://www.ntcompatible.com/forums/viewtopic.php?t=26626&highlight=dns+domain Let me know if you are still having issues with it.

I got this from DotNetJunkies, and it's pretty cool. http://www.frozentech.com/content/livecd.php It's a list of all current distros providing Live CDs. So, what's a "Live CD"? Well, typically running this disk at boot lets you run whatever distro on it without having to install it. It's very cool for: 1. Introduces newbies to Linux, without having to sacrifice a currnet installation to do so 2. Lets you repair systems that are currently running Linux (or even other OSs, depending on the distro and kernel options/modules used) while within a Linux OS (including chroot, for the most part) 3. Looking cool around your friends because you are 1337 and running Linux on your machine, even if it isn't installed What is really cool about the Gentoo disk, is that the basic installer would let you run an SSH server from the CD's kernel. This enables you to install Gentoo on a system over the wire. I was able to install a couple of Linux boxes for a LAN party a couple of states away in this manner, and it was very handy. Once I had the kernel compiled and ready to go (with a new SSH server installed and configured to launch at boot), I just had his girlfriend eject the CD before I rebooted it. Once it came back up, I could continue the installation on the fresh, new installation. Very trick.

OK, that's pretty cool. I'll have to check that out in the lab at some point. Nice find.

Are you running Active Directory, or is this network a member of an NT4 domain? What makes you think DNS is the issue (certain errors, checking network traffic, etc.)?

So the disk will not boot, or you installed the OS and the installation will not boot? What error(s) are you getting? Gentoo requires more manual installation than most other distros. I still have to burn my ISOs tonight, so I'll check it out later.

Just to clarify, if you would like to run Gentoo as a desktop from a Live CD, get the image for Unreal Tournament 2003. It has a demo of UT2003, can accelerate nVidia cards, and runs Fluxbox for a desktop from what I remember. This image is almost a year old though, and that may be a turn off (I thought they were still up[censored] it). The current disks will run Gentoo in a command line interface (CLI) and also lets you install it from any of the three stages available.

Nice. Gentoo is my fav. After that is Debian.

Sorry, but we cannot condone the use of keygens, serial databases, or any other means of gathering w4rez. I am sure there are tons of places you can get the information from (albeit illegally), however we can't allow it to be posted here.

If you are in workgroup mode, you need both systems to have the same account and password, and it would help if they are in the same workgroup. What happens is your client is hitting the server up with guest credentials by default, and thus getting denied since you don't have that account enabled (and with good reason). This thread can explain it a bit more: http://www.ntcompatible.com/forums/viewtopic.php?t=26664&highlight=guest+account What you are looking to do is much easier if you were using Active Directory, and made the XP box a member of its forest/domain.

Don't know bud. I would get a hold of someone else's video card, or maybe even check out the PSU and see if the current one is flaking out. Can you try installing XP on the 10GB disk and see how it runs? It doesn't seem like it would be the OS (this is typical of a hardware problem, and this can help determine if the 40GB disk is going out) but it might be worth a shot.

Remove extraneous hardware (sound card, NIC, etc) and leave just video support on the system. Boot up, and see if it comes up. If it does, add one piece of hardware back in at a time until you find the failure point. Also, see if you can update the BIOS of the mobo (if it can be done with a DOS floppy, that is). I would also remove the 10GB harddrive during the first boot sequence. I have had old drives cause lockups in the past during boot because they died (and you didn't indicate if the harddrives were tested with the other equipment).

See if you can use the recovery/emergency disks that you get when you install McAfee. Then, boot the system with the floppies and scan for it then. Also, look up the virus at McAfee and perform whatever steps are indicated. http://vil.nai.com/vil/content/v_100516.htm#RemovalInstructions If you go there, you will see the simple directions of "can all files with the issue". However, WinME and WinXP both have system restore running by default, and that service has a lock on those files which will keep you from deleting them. So, you will probably want to disable system restore, rescan, delete the viruses, and then patch the system if possible. Then, reboot, and rescan with the offline virus removal tool to make sure. Rinse and repeat as necessary...

I doubt those will address the issue, as this is a major drop in speed and not some minor drop that you are trying to tweak. If you don't want to use RRAS, that's cool. I just feel that setting the server up as a router (which is what are you trying to do with linking the networks) would be better suited with RRAS. When a server has two NICs sitting on the same segment (and not bound together to form a virtual connection) you can get odd behavior. Setting it up as a router using two different networks would be a good solution. You can find walkthroughs (like the one I posted earlier) all over the place to set it up. If you can properly administer IIS, then this will not be an issue. Otherwise, get a separate router as suggested earlier.

I was basing workload off of him having XP Home and XP Pro comprising his network. With this layout, I don't see much of a workload. Setting up the firewall should be done by most people anyway, so security wouldn't be changed (probably increased) with the use of RRAS. Plus, he gets to save money and space by not using the router. Not a bad deal overall.

Just to clarify, but there isn't much going on resource wise for Windows 2003 server to route traffic, especially in this scenario. In addition, setting up the simple firewall in RRAS would make the system (and network) quite secure. You can later setup the server to host VPN connections as well, in addition to other technologies that consumer routers have issues with.

Quote: Wicked! I had the same problem, bumped the DNS entry for my server ahead of my ISP's and PRESTO! Worked a treat! Too bad this isn't better documented, can't believe microsoft wants u to call em! hope those that do don't have to PAY Thanks for the tip It is documented, but it's documented in areas that refer to initial setup. This is something that should be done on most (if not all) DNS setups. You want to have the DNS servers pointing to each in their respective IP settings, with forwarders pointing to parent domain DNS boxes (if applicable) or outside DNS servers. For example, if you had parent.com and a child domain named child.parent.com, you would want the parent servers pointing to each other in their IP settings, with delegations for "child.parent.com" pointing to the child DNS servers, and forwarders pointing to outside DNS servers. In the child DNS servers, you would have them pointing to each other in their IP settings, with forwarders pointing to DNS servers in parent.com. This way, you completely control name resolution throughout both domains from the root (parent.com). All member servers, clients, and any other system that needs to resolve internal resources would have the corresponding DNS servers in their IP setting for their domain (member server in child.parent.com would have the DNS server IPs for the child domain in its IP settings, while an admin client in parent.com would have the DNS IPs for parent.com in its respective settings).

Ahhhhh.... Very good. It looks like you had it going ok, but going with RRAS will probably be a better solution.