Author Topic: Crazy problem Need some help (Read 407 times)

Reschke · « **on:** February 24, 2007, 09:18:28 AM »

OK here is the deal.

I have two computers running one running WinXP Pro SP2 and another (newest one) running WinXP Home SP2. The main family system is the XP Pro setup. It has been running great for a long time except for having problems in AH. The other is my most recent build and was supposed to be my main gaming rig, however it refuses to connect to either my home network of directly to my cable modem. I use the onboard NIC for both systems and the XP Pro connects automatically.

I was using a wireless network card in the XP Pro for a while and the router took a dump and now I am back to a wired connection while I am waiting on a new router from Dlink. So I have to swap (or try to) the cable back and forth. My cable provider is setup as a DHCP BUT they have for troubleshooting reasons told me to use two different IP's for the computers. Still only one of them will connect at all and when I try to use the same settings as the XP Pro system the XP Home system refuses to connect.

If anyone has an idea please let me know.

Basic system specs are:

XP Pro system:
AMD Athlon64 3200+
Gigabyte K8N Pro
1GB PC3200
BFG 6800OC

XP Home system
E6600 @ stock speed
EVGA 680i
CORSAIR XMS2 DOMINATOR 2GB DDR2 800
EVGA 8800GTS with 640MB

Irwink! · « **Reply #1 on:** February 24, 2007, 09:51:16 AM »

In Local Area Connection, TCP/IP properties is it configured to obtain an address automatically (from DHCP)? If it is then you can go to Run, type CMD to get a command prompt and type "IPCONFIG /ALL". If it comes up with anything that starts with 169.xxx.xxx.xxx then it's trying to get an address from DHCP and for several possible reasons is not getting a response from DHCP and is just giving itself what's called an APIPA address. If this is happening one quick solution is to manually configure TCP/IP properties and give the computer an address you know is in the correct range for your router. The range likely begins with 192.168.1.xxx. If you do wind up giving the computer an adress, then also configure the "default gateway" address as the address of the router - likely 192.168.1.1. That's the way many home routers come configured from the factory.

Reschke · « **Reply #2 on:** February 24, 2007, 11:44:22 AM »

Thanks I will give that a shot today and see what happens. If it comes down to it then I will reinstall XP Pro on that box and ditch Home.

Irwink! · « **Reply #3 on:** February 24, 2007, 01:22:23 PM »

Quote

Originally posted by Reschke
Thanks I will give that a shot today and see what happens. If it comes down to it then I will reinstall XP Pro on that box and ditch Home.

That is almost certainly not the problem. Good luck, you'll figure it out.

Reschke · « **Reply #4 on:** February 24, 2007, 03:14:44 PM »

Well that did not work at all so I am going to dump XP Home and try XP Pro on that box. I think I have done something to the settings since it would work and I really don't have the patience with this system since I want to get it running my games and I don't feel like screwing around with it anymore than necessary. I just need to download the SP2 to a CD and have it ready since my XP Pro disk is pre SP1.

DAVENRINO · « **Reply #5 on:** February 24, 2007, 03:23:18 PM »

Have you got a PCI NIC you can try? I am using the onboard on this rig but have had problems with them in the past.

Also, regarding the reinstallation, some newer board SATA/Raid setups won't work with older XP disks unless you have slipstreamed SP2 with it. I was lucky and borrowed an XP Pro SP2 disk from a friend that accepted my XP Pro key. It failed when I tried his newest disc.

Reschke · « **Reply #6 on:** February 24, 2007, 03:44:58 PM »

I might have a PCI NIC laying around....unless I donated it for tax reasons before the end of last year.

MrRiplEy[H] · « **Reply #7 on:** February 25, 2007, 02:30:44 AM »

A common scenario is that you are limited to only one public ip address by your provider. This might be the reason why they recommended using different ips i.e. NAT.

Simplyest solution is to get a router/firewall box and use the internal dhcp server to distribute ip's as you apparently are going to do. Why it takes so long to get a simple router? This should be on-the-shelf stuff on any retailer.

Just FYI I've found (through experience) that D-link products are extremely low quality, at least on wireless side. I will not touch it any longer.

humble · « **Reply #8 on:** February 25, 2007, 09:06:33 AM »

You dont specify the MB your using with the 6600 system but it's almost certain to be a pci-e board. XP Pro will not load since it doesn't have the drivers for pci-e until SP2 (at least thats been my experience). Since the MB I was using didnt have the drivers broken out I couldn't mess with F6 during install. I dont know if you can insert them like you can raid drivers etc.

If you cycle thru the setup till the end (last thing will be the FAT32/NTFS) and then blue screen to an error message with pci.sys at the bottom thats what your problem is.....