Search results

Hmm, good point. If your 'modem' is actually a router, you will need to bridge it and disable NAT in order for your port forwarding to work as prescribed. Double-NAT'ing causes all kinds of problems and should be avoided when possible.

Hello, welcome to HWF. What you are trying to do is called "PAT (port address translation)" in more standard networking terminology, but D-Link calls it "port forwarding" in this case. In the product manual on page 31-32 you can find D-Link's directions on port forwarding. Once you've read those...

install windows xp Pro SP3 from usb thumbdrive - Google Search

Interesting, but it still should have been able to boot fine with the RAID rebuilding. You can check the status of a Linux RAID like this: cat /proc/mdstat

I see. CentOS is a good choice then, though you will have to tweak Samba out of the box a bit since their default rollout is a bit broken. Still, after a little TLC it works great, and I've found it outperforms a "real" Windows server about 2.5:1. Also, I have a lot of experience consulting...

It's probably a buggy implementation of ACPI or IRQ steering in the mobo. Try interrupting GRUB and using some of the following boot options (one at a time, of course): irqfixup irqpoll noapic nopcmcia apm=off pci=noacpi acpi=off lba32 If any of these work it can be the basis for further...

Red Hat / CentOS use quite an older kernel, since it is supposed to run on stable, primarily tier-1 hardware in a business environment. ASRock is not exactly know for their reliability or compliance to standards, so it's entirely possible they just don't play nice together. But, first things...

It really depends on the OS you're installing much more than the hardware itself. With Linux, just put it on a USB thumbdrive and install that way. With Windows, you can use an external DVD drive to do the installation. Or, depending on the version, you *might* be able to use the thumbdrive...

Kernel 2.6.30.5 available 2.6.30.7 is built and syncing to kernel.hardwareforums.com. As a bugfix release, it is recommended for anyone running a 2.6.30.x kernel. Get it here Changelog

Connect-debounce failed errors typically mean the connection to the device is not reliable. Most likely, it means that either your adapters are defective (either by design or manufacture), or that the device you've plugged it into is incompatible. I'd guess the former based on their source...