clutch

Well, it sounds like it could be the drivers, since it may be a native USB device. However, 200Hz isn't such a great option, as it just eats up more CPU cycles. ------------------ Regards, clutch

Nicely Done! Thanks. ------------------ Regards, clutch

I just got roadrunner, and they gave me a 3Com modem. I have a server and 2 workstations, and they are all linked thru my newly purchased Linksys router. They are cheap (this one was $169--$149 after rebate--at Best Buy) and work fairly well. This one has a built-in 4-port switch, but there are units with just the link in that are about $40 cheaper or so. Took about 5-10min to setup, and it was done. My ddns client (TZO) works fine, as do my mail, web, and ftp ports. Plus, I can host a game of Q3. If both of your machines are already connected on a LAN, then the router is the easiest. Otherwise, you can use ICS or some other proxy and install that on a machine with 2 NICs. If you just have them connected with a crossover cable, then just get a router with a built-in hub/switch and save some more cash. BTW, I am not a fan of proxy software or using a PC as a router, in case you haven't noticed... ------------------ Regards, clutch

OK, IPX/SPX ------------------ Regards, clutch

You *may* have to reinstall it under the other accounts. And then, due to the NT underpinnings, you may not be allowed to do so unless you grant admin privies for the user account to do so. ------------------ Regards, clutch

Yeah, the DOS reference was interesting. I do use a DOS 6.22 boot floppy for NT installs that have FAT system partitions. Just wanted to state that it *could* be done... ------------------ Regards, clutch

Get the latest Service Pack (6a at the moment). This was fixed in SP4 I believe. ------------------ Regards, clutch

I'd like to see that with NTFS without something from Winternals... ------------------ Regards, clutch

Stay away from NetBEUI. While it's a faster protocol for MS OSes, it's a workaround for authentication and other issues you may have. Just use straight TCP/IP. ------------------ Regards, clutch

I have a Cisco 1720 at work, but I haven't heard from any home users of their products. I will check out their site tho. Tnx. ------------------ Regards, clutch

I periodically run a DOS 6.22 server (486 box). Would run Linux, but I can't find drivers for the IDE controller. ------------------ Regards, clutch

Well, it will probably be a long wait for SP2. BTW, how is DNS doing? I know that with the base config, it had quite a few issues to the point where it wouldn't work. But it works quite well now, it's just a matter of tuning it to your needs. The NT4 WINS/DNS combo was "dynamic" enough (you could have WINS update the DNS with its own database thereby having the dynamic registration) and seemed to work well. I am not sure why this new version has to be so complicated. Oh, and one other thing. If this server also acts as a DNS server, it *could* be looking for another box to replicate its database. If you have a decent packet sniffer, run it on another box and watch what happens with your AD server at boot up. A TON of traffic comes pouring out. ------------------ Regards, clutch [This message has been edited by clutch (edited 04 December 2000).]

Actually, OLEerror is on the right track with that comment. Some side effects of AD (herein referred to as A.D.D.- Active Directory Disorder ) cause a ton of traffic to fly across networks, including over routers and such to ISPs. In my case, I have to practice setting up the DHCP and DNS services for the upgrade exam to Win2K. There are many new and wonderful errors ***ociated with A.D.D., including DHCP anomalies where the server waits for authentication to service the local network. Since A.D. needs Win2K DDNS (which in turn loves DHCP), you can't get long delays in waiting for this authentication, only to have the DHCP service denied. In addition, I found numerous erros with the Win2K DNS system, which led me to narrow downt the important errors to 4, and then hit Technet to resolve them. Some of these problems (like A.D. claiming DDNS is disabled, when it may not be) have fixes that you can pay for or just wait until SP2 to get them. What I did to resolve most of the wait time, was lock down the router further by canning the bootp port and a few others in order to allow DHCP to work again. It did shave off about 2 min off the boot time, but SP2 should kill most of the issues (I hope). So, while A.D. may not be directly causing the problems, it is due to A.D. that you are having them. WinNT DNS didn't have these issues, so I am hoping the DDNS will get worked out. ------------------ Regards, clutch

I have been drinking a lot of Diet Sprite lately. Not too bad. Caffeine makes my sleep apnea worse. ------------------ Regards, clutch

Simple things first. Can you ping the other machines on the network? If so, what name resolution method are you using? WINS? DDNS? WINS is a lot easier and is great for small workgroups. If you have it installed on the server, setup the clients to use it under the TCP/IP properties panel. If you need help, just email me. ------------------ Regards, clutch [This message has been edited by clutch (edited 03 December 2000).]

So how is the new card working for you? ------------------ Regards, clutch

Quote: Originally posted by DosFreak: YAY! DOS frenzy! I had a feeling you might appreciate that after I posted it. Batch files for everyone! ------------------ Regards, clutch

Cool, as am I. ------------------ Regards, clutch

LOL ------------------ Regards, clutch

sarcasm Or you could simply hack all the tech support databases with your ideas, and then the country would be paralyzed in a DOS-frenzy... /sarcasm Don't take things to seriously.... ------------------ Regards, clutch

According to CrazyKillerMan, it doesn't sound so hot... http://www.ntcompatible.com/ubb/Forum4/HTML/000190-2.html ------------------ Regards, clutch

I love the nVidia stuff, but I would go for the V3. Way better framerate vs the base TNT. ------------------ Regards, clutch

Whenever I have a system problem like that, I reinstall the last service pack that I used on it. It fixes the problem about 85% of the time. ------------------ Regards, clutch

Canada? Is that the place that has all those beer commercials with the bear? ------------------ Regards, clutch

You have to update the routing table on the server. That's why you can't ping across it. Normally, a current model router will have dynamic up[censored] ability, which would alleviate you of this chore (though some high end units require you to add routes or conduits manually). Check out this link: http://www.ntfaq.com/Articles/Index.cfm?ArticleID=14983&SearchString=routing Like I said before, I don't mess with this since I use routers and firewalls instead. But it should work fine for you. ------------------ Regards, clutch