AWS

Tracing route to pcp05837078pcs.jdover01.nj.comcast.net [68.***.***.***.Ip_removed] over a maximum of 30 hops: 1 2 18 ms 17 ms 25 ms 209.212.174.237 3 18 ms 21 ms 17 ms 207.251.180.230 4 19 ms 18 ms 27 ms 0.so-0-0-1.hr1.chi2.alter.net [152.63.64.181] 5 18 ms 17 ms 19 ms 0.so-6-3-0.xl1.chi2.alter.net [152.63.73.34] 6 18 ms 17 ms 18 ms 0.so-7-0-0.br6.chi2.alter.net [152.63.71.94] 7 21 ms 20 ms 21 ms 204.255.168.58 8 20 ms 21 ms 21 ms tbr1-p013902.cgcil.ip.att.net [12.122.11.205] 9 41 ms 42 ms 41 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1] 10 40 ms 40 ms 46 ms gar1-p310.nw2nj.ip.att.net [12.123.219.130] 11 42 ms 41 ms 42 ms 12.119.12.18 12 42 ms 43 ms 46 ms ar01-pos-9-1.dover.nj.nj03.comcast.net [68.87.19 .246] 13 43 ms 45 ms 42 ms fe-0-0-ubr02.dover.nj.nj03.comcast.net [68.87.52 .38] 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. Pinging 68.87.0.52.38 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 68.87.0.52.38: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) Tell them you are getting 100% loss on the router after your gateway. I am amazed that you can even get here.

Tell them you get ping timeouts on your gateway. Have them do a traceroute back to you and they should see where the problem is. You'll need to get to a second level tech. Have them connect you with a manager right away.

I figured it wouldn't help. One of their routers is having problems. Try here for help: http://www.dslreports.com/forum/comcast There are some Comcast techs that hang out there. It is possible that Comcast is doing the upgrade to their network. I know that while the upgrade was going on in some areas the kinds of problems you're having was commonplace.

If you're getting timed out messaages then the problem is on the Comcast network. Use 66.93.186.15 as the only DNS server and test again. This is my DNS server. If you still experience timeouts post back.

Take a look at http://kernel.org That is the pivot point for kernel devel for Linux.

This isn't a browser issue and if tech support told it was they're crazy. The DNS server that you are using is the problem. What you should do is search for a DNS server near you and use it. The problems will go away. It is also possible that your experiencing high latency. This would be caused by too many people on your node.

I was wondering the same thing. I looked at the logs and it was spiders. Seems all of them hit at the same time. The same thing happened at the .net forums when it first opened. I would think that in the next couple weeks we will see an increase in traffic and users.

I run 3 Windows 2003 server. This site is running on Enterprise Edition. One of the biggest improvements is 2003 out of the box is locked down. You have to turn on the services you want running. It's much easier for an admin to configure the sevices you want running instead of shutting off the ones you don't. I'm not familiar with clustering on 2003. I always used FreeBSD.

Yep it works.

I'm sure once MS gets the OS out the driver will come. Probably be the same timeline as when MS went with the certified driver program. It took some vendors a while to pass the test. I remember when AMD entered the duallie market. It took over 6 months for C-Media and Creative to get a stable driver out. Blue screens every time you played 2 sounds at a time. I'd have an mp3 playing and if I got a new mail alert blue screen.

WOW. I didn't see that one. All the rumors floating around were that MS would delay XP64 until Intel released their chips. It looks like an alliance between AMD and MS will build. This alliance could bring the mighty Intel to its knees.

From what I'm hearing the nForce chipset performs well, better than AMDs and VIAs. I'm not sure on availabilty however. Only x86/64 boards I have seen are with AMDs chipset. With MS decision to roll out service pack 2 for XP and delaying XP x86/64 it might be a while before many boards are put into mass production. While Suse and Mandrake have a port for x86/64 until MS gets in the game not many people will be in a hurry to switch. Rumors abound that MS is slowing development because Intel is going to get in the game. My suggestion would be to wait a few months to see what shakes out.

Happy Holidays and have a safe trip.

It allows you to use more than one IP and also alows you to have 2 net connections and one for lan between computers. In my case one is assigned the site IP and IIS uses that one connected to the router. One is a direct connection to the db server. The third has a second IP assigned to it and connects to a hub so the box can act as domain controller.

If you install XP or 2003 now you have to disconnect from your network, install and then boot into the OS and turn on the firewall. After you do that hook backup to the network and head to Windows Update. Install all the patches and then if you want you can disable the firewall. If you install connected to the net you will get hit by msblast within a few minutes. I was hit with it while I was installing 2003 Enterprise. Got DCOM error as soon as the network was configured. My mistake. I have 3 network cards in the server and I forgot to diconnect one. Service pack 2 enables the firewall by default as will all future releases of any new MS OS. As far as anti-virus I use NAV Corp on the servers and NAV 2003 on workstations.

There was an email by Linus Torvalds that I read yesterday. He said that the SCO claims to some of the code is flatout wrong. He wrote the code himself in 1991. SCO under pressure released the source to the disputed code and after Linus looked at it he found bugs that he admits to putting in the code because he was a newbie and made newbie mistakes. I'll post the article later this evening.

I'll setup RSS later tonight after I get home. I had it on my todo list and when I got Longhorn I forgot about it.

There isn't a person in the security field that has one iota of respect for him. He spreds fud and does so in a manner that makes real security experts dislike him. His claims have been debunked so many times it's laughable. A person that visits his site, if they don't know anything about the internet or computers, will come away thinking that they can be hacked by just turning the box on.

In good time. There will be more and more added as we go along. I'm hoping that users will also contribute.

Yes it will be and welcome.

I know. I've been trying to figure a way to fix that. Will probably have to run a querry to change the cat id.

Yes it will happen. I want to get the site running smoothly before I format and install an OS on the dead server.

The first versions of P4s 2Ghz and up were built on the same chip as the Xeons. In theory hyperthreading should work on these models if you have the correct motherboard bios, one that allows you to enable them. I was involved in a 100 page thread at HardOCP when someone happened to se the same thing you did. It seems that Intel disabled HT somewhere on the chip. If this processor was just bought in the lasy 3 months then it is probably a P4E. If it is one then HT is enabled in them and the only thing you need is a motherboard that supports it. Is the processor an 800Mhz version or is 533Mhz? If it's an 800 it's HT enabled.

Along with that error you should get a path to a module that isn't loading. Once you fix that it will start. Unreal has a bug in it that causes to happen what happened. Bring up task manager and click on precesses tab. Look for wircd.exe and kill it. If you have services running kill it also. Then restart Unreal.

UnReal and Apache don't integrate together. Each is a stand alone server. What kind of error are you getting from Apache or is Unreal giving you the error? Check your event viewer. When Apache errors it writes an event to Windows event log. If UnReal is giving the error take a look in the directory where Unreal is installed. There will be an error log. Post the errors you're getting.