Hi guys!I really hope someone can help me with this really confusing problemI recently got my old 386 reenabled by installing and running a Linux Coyote router/firewall, thus freeing up some resources on my main/FS computer that also acted as Internet Connection Sharing (ICS) Server. The Linux router works flawlesly. But here's the thing.It seems like my Network card (NIC) on the former ICS server (main/FS comp) isn't able to respond to requests. The NIC works when it is the initiating part. I.e Internet or Ping to another computer. But as soon as I try to Ping it or run DirectPlay sever between it and another computer it refuses to respond.I tried with two different NIC's that works perfectly on another computer.I tried DHCP assigned and fixed IP-addressingI tried to change port on the switch to one I know workI tried to change cables with one I know workI tried another PCI-slot. Both had NIC's when I ran ICS and they worked.I tried with and without NetBIOS supportNo firewalls on any computer except the one running the Linux routerNo conflicts on IRQ (The NIC uses IRQ3).No conflicts in subnet masksLates BIOS installed.Latest NIC drivers installed.Uninstalling and trying to manually clean up after ICS.Uninstalling and reinstalling the TCP/IP protocollUninstalling and reinstalling the NICNow I've run out of ideasEqpmt is:Intel 800MHzWin98SE384Mb RAMHD 2 partitions 2.00/1.12Gb and 25.9/16.5GbNIC 3C905B-TXPlease guys. Give me some good advice on what to do or what could be wrong. LET'S BRAINSTORM!!! Life is simple: Eat, sleep and fly!Mats Johansson / SAS526

It would seem the original computer still thinks it is the server. Open system properties by right clicking your MY COMPUTER Icon, select the performance tab, click on file system, click on hard drive tap, change the role of this computer from network server to destop computer, click ok, and follow any instructions.I don't guarantee this will fix anything but it is worth a try.

The setting is already on Desktop Computer. Sorry... :-)I'm beginning to suspect some left behind registry line from MicroSnot ICS software.

More than likely. That's why I bought a router vice using one of my computers.

You're a clever guy! ;-)I just thought I would tell you that I solved the problem. It was, as I thought, the Microsnot Internet Connection Sharing software that did leave a malicious trail behind.In the registry HKey_Local_MachineSystemCurrentControlSetServicesVxD the little ##### left two keys called "DHCP" and "DHCPOptions". Taking them away (after a registry backup) made the NIC behave as normal.God I hate the Registry!!! Life is simple: Eat, sleep and fly!Mats Johansson / SAS526

Congrats - the registry can be good or it can be bad! Leastwise, you became a little smarter being able to dig around in your important files and not have to do a complete reinstall.I don't understand why some of the posters have had to reinstall FS2002 so many time. I am on my initial install from about Nov 01, and I have made plenty of changes in air files, scenery, on and on.Again congrats - now as you say! eat, sleep, and fly!:-lol