clutch

I get faster performance in Q3, and haven't had any issues with XP Pro. I still like Win2K though, and I feel that support will be around for a while to come since most companies have planned Win2K/AD deployments *this* year, and because of that will probably not fiddle with XP much.

Well, you can still write the ASPX files in anything (like Notepad), but you still need some sort of database application which you haven't listed yet. Getting VS.NET will not necessarily solve your problem unless you install MSDE 2K from it, or some other SQL DB server app.

What database application are you using?

Try the online help first, and I would recommend getting a book. If you want it to work properly, then you will need to familiarize yourself with (D)DNS as well and most books from publishers such as Sybex and Wrox will cover side topics such as this quite well. Many people just try to "get it going" and wind up reinstalling it over and over again to correct problems, or they just watch the event logs pile up.

SDRAM or DDR-SDRAM? I have seen the price of DDR-SDRAM go up more significantly than regular SDRAM, and I think that's what BladeRunner was alluding to.

Read it? Hell, I sent it to everybody I know (and both of them thank you, THC).

If you can, just make the jump to some form of SQL or MSDE 2000 (which comes with Office XP, VS.NET, Visio 2002 and some other programs) as those natively support multiple connections. I experienced the exact same problem you found, but since I only had one DB that was in Access and I was going to upgrade it to MS SQL, I didn't fiddle with it any further. At one time, I could have the site running *and* be able to connect to the DB in Access or Visual Studio to modify the views (queries) for tuning.

No, I would highly recommend that you do not change your motherboard and retain the same OS installation, due to major differences in architecture and the harddisk subsystem that might be present. It *might* be possible that your changeover from one type of processor to another could be causing these issues (although I thought people have done this with Celeron to P2/3 CPUs before), but I haven't done that before myself.

The Dells rock, that's what I get for our Engineering staff to run Solidworks on (and for myself later this year). I don't believe that there are a ton of laptop makers that have GeForce chips available, and I wouldn't waste my time with the ATI chip yet.

Or you know how to use QCHAIN: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q296861

LOL, I thought I was crazy, but I had the same issue. There was something recent that did this, because when I used system DSNs I could connect as many times as I wanted and not get the error, but I can't do that anymore (no bother, as I use SQL 2000 anyway, but kind of annoying). What have you done recently? Have you upgraded to MDAC 2.7? You can get that here: http://www.microsoft.com/data/download_270RTM.htm You might have applied a patch recently, so let's see what was done.

How much do you know about IIS? That would *normally* be the default site location, but I always disable and remove that one and locate my sites elsewhere. Did you do the same thing? Are you trying http://servername/tsweb to get to it? How about http://serverip/tsweb ?

Got the newest BIOS update?

Do you have IIS properly setup? Are you sure you have Terminal Services setup properly? Did you extract the webpages and components to the default directory on your site (/tsweb)?

A couple of quick things to check. First, for some reason did the database NTFS permissions get switched to "Read Only"? Also, do you have another app using that ODBC connection, or do you have Access itself connected to it at the same time?

You want NetBIOS over TCP/IP enabled, and you want them to be in the same workgroup. Once those are set, make sure both machines are online (just booted on the network) for about 45-55 minutes to make sure that any cycling is done for Network Neighborhood. Then, tell us how it goes.

Are they both setup as members of the same workgroup? If you are logging on as admin, is that the admin of the workgroup they both participate in? What is the IP configuration of the systems on your LAN? Do you have NetBIOS over TCP/IP enabled?

Well, it is true, but AMD is also notorious is for rating their procs very close to their absolute limits anyway, which is why they tend to run a bit warmer than their Intel counterparts at the same speed. Right now, the fastest Xeon with 1 or 2MB of cache is 900MHz, and those are both expensive and rare to get a hold of. Remember the hard time AMD had with the 750MHz+ Athlon classics and their external caches? AMD had to drop the cache speed dividers from 1/2 to 2/5 in order to keep on making "faster" (faster in clock speed anyway) processors to keep up with Intel who was using onboard cache by then. Up until that point, AMD was making all kinds of promises about cache configurations that would go up to 8MB on a single processor. However, I have yet to see them get beyond 512KB at any speed, while Intel has had 1 and 2MB variants out for a long time, and that's why they are popular in the server market (among other reasons) because large cache amounts help a great deal in database applications. Onboard cache lends itself heavily to the performance of the processor, but at the same time can increase its chance of failure at high speeds. That's why the Celeron "A" did so well, since it used a really small amount of on-die cache that ran at full speed vs. separate cache chips, and they smoked the equivalent PIIs in some apps (like games) while they would fade out in other apps (like SQL/Oracle apps) where larger caches were more useful. But those same PIIs couldn't overclock much at all due to the cache amount/configuration, much like the current AMD crop has problems because they are already running close to their thermal limits as it is.

The cheaper chips have smaller and/or less complicated onboard caches, hence the ability to overclock higher. If you notice the large cache Xeons (like 1MB and 2MB models) are still stuck below 1GHz due to the large cache amounts.

If stability and compatibility aren't concerns, then yes price is a great reason to go with AMD. AMD Processors are fast, but I hate the chipsets that I have personnally been exposed to that run them. Sometimes I wish that Intel would run their processors to the same temps that AMD is willing to, so we might see some interesting performance ratings. But having a CPU that runs quite cool even in a manufacturing environment (where I have some PCs at work) is nice as well...

I have had many ATI and nVidia cards at home and work, and I would have to suggest the nVidia cards for stability and speed. The last time I had a problem with an nVidia-based card was when I had a GeForce2 Ultra that I was trying to install on my Apollo Pro 133a based board. That was more a failure of Via than nVidia, however.

"Rad" LOL, I haven't heard that one in a long time! Wasn't that a movie once? I think it came after a movie with Nicole Kidman named "BMX Bandits"...

What are you talking about? The taskbar grouping where similar programs get bundled into one entry on the bar? Right click on the taskbar, go to properties, and select the Taskbar tab. Then clear the "Group Similar Taskbar Buttons" checkbox.

But before you installed lockdown, it worked fine? That's weird, I have used it on 6 or 7 servers myself without any issues from normal websites (Outlook Web Access takes more fiddling). If you run it again and uninstall it, it works fine? And, do you now have a urlscan log file in the directory I mentioned earlier?

I had a Linksys BEFSR41 in use before going to ISA server, and I used it to host: 3 Websites 3 Terminal Services Connections (2 using changed ports) 2 FTP sites 1 Exchange Server 1 SQL Server Remote connection 1 Q3A Server occasionally And it worked with all of those very well. As for the NetBEUI issue, have you tried direct attempts using \\pcname\sharename to and from the XP box? Also, if you are relying on Network Neighborhood to find computers and their shares, then you should know that it could take about 50 minutes or more of a system to cycle into the Master Browse list (which is where the Network Neighborhood is pulled from), during which you will not see the computer's name. And, since you are now using NetBEUI, make sure to disable NetBIOS over TCP/IP since it just broadcasts your system info over the IP protocol, and you probably don't want to share that information with everybody. One more thing, you don't, by chance, have the firewall enabled on the XP box do you? Normally this is something that is turned off for troubleshooting, but I am just checking. Since you have all 3 of these machines running wide open to the internet, having firewalls on all 3 would be the obvious thing to do. However, you want to treat them as if they are on the same LAN (when they *should* be on a VPN, but that's probably not going to happen) so they can share files locally. You *really* should just have all 3 behind a NAT device, and that would make life MUCH MUCH easier and more secure, but if you are determined to rig this, then you should probably bind NetBEUI higher than TCP/IP on the NICs of all 3 machines, and then heavily lock down TCP/IP on all 3 machines. I still think it's a really bad idea going this route, but that's just my opinion.