Hey Guys,

I need help getting my dual core Xeon (Asus PC-DL Deluxe MOBO/2 533 processors/Win XP Pro SP2) to talk to my new I7 Quad core PC. I need to set it up as a remote PC to work through the I7, as if it were a docked laptop. That way I can keep using my KVM switcher for a dual PC rigg.

The problem is that the dual core Xeon will not let itself be seen by the I7 PC. The Xeon will ping the I7 but the I7 cannot ping the Xeon. I've tried everything that I can think of. I tried a direct cat5 crossover cable to make the 2 PC's connect. Once the Xeon showed up in the I7 network for a second. But when I tried to open the link, it denied me access, saying that it couldn't find it (??). It never came back after that. I tried using a Linksys router to accomplish this. Same result. Showed up once on the I7 and denied me access to the dual core drives, never to return afterwards.

I've gone into services and activated everything that has anything to do with networking and internet connection to get this thing to talk to the new PC and nothing is working.

I thought the Xeon's ethernet port might've been bad. But it has no trouble connecting to the internet. So I'm not sure if that's the problem or not. I did download the latest intel drivers last night. But that didn't change anything. I'd purchased a second ethernet card (also a Linksys T100) a couple of years ago. But I couldn't get it to ping through that port either. Now, while it shows up in the device manager and says that it's working properly, it does not show up in the network connection window at all. So I also uploaded the latest drivers for that. No change. Now, I can't access anything through that port. I tried running cat5 cables to both the Asus MOBO port and the Linksys port. Linksys still won't show up in network connections and the intel port still won't allow anything to ping it.

I've opened all the sharing protocols for all of the drives and folders. Nothing. In fact, I can't even open the WORKGROUP network inside the Xeon itself! I don't understand how it can ping the I7 but it will not allow itself to be pinged. I've never understood tha mapping procedure in the networking section since it won't let you select drives :a, :b, or :c. So I couldn't use that option either. Everybody keeps telling me how simple this process is. But when they try repairing the issue, they all leave scratching their heads.

BTW this feature has never worked. Not once in all the years I've owned it! I've had numerous techs out to solve the problem and each has gone home defeated. All these years I've been working around this problem by using data transfer applications like Fastlink or File Mover. It wasn't ideal, because it wasn't in real time. But it was okay and since it was only a 2 PC rigg, I got used to working like this between the KVM switcher. But now that its a 3 PC rigg I HAVE TO GET THIS THING TO DOCK WITH THE I7 or just get replace it!! As I just spent a small fortune on the new PC upgrade, this is not the solution I'd select! The Xeon works perfectly except for this one major stumbling block. This is so frustrating! I've been working on trying to fix this since last Friday!!! So we're talking 5 full work days devoted to nothing but this BS!

Can anybody help me figure out this ONE WAY PING PROBLEM??? What do I have to turn on/off in services, BIOS, whatever to make this thing accept a ping from another PC (The AMD PC couldn't ping it either)??!!!??

____________________________________________________________________________________
Nuendo 4.3.0 thru 1.6
ASUS P6T SE Quad Core i7 with i7 Processor
24GB Memory
Windows 7 Pro
Asus PC-DL Deluxe MOBO/2 533 processors/Win XP Pro SP2
4GB Memory
1 Midex 8
RME Ray-Dat
UAD-1 Ultra Pak
Apogee Big Ben
GS3 on AMD Athlon 64 3200+ (2.0Ghz)
4GB Memory
Panasonic DA7 Mixer