0

I have a XP Pro box that will not accept any incoming connections.

It's not the built-in firewall.

The only thing I can think of it that this box is still part of a domain and domain controller no longer exist. The other computers are not part of the domain.

Any idea what would cause this box to stop accepting connections?

1
  • The firewall is completely turned off. I gave the box a static IP. The cable is good. (I'm using the box to access this site.) It has trend micro anti virus. I have never known it to be problematic. The box can ping other computers on the network. It will not return a ping or HTTP requests. It will return a ping and a HTTP request to it's self. So 192.168.1.83 brings up the web site running on it.
    – NitroxDM
    Nov 26, 2009 at 2:44

2 Answers 2

1

Could be that the antivirus software has its own built-in firewall. Can you ping the box? If you can't, it's almost certain that a firewall is responsible. One other possibility that the PC is not online (wrong IP, bad cable, unplugged at the switch, etc.)

1

By "it is not the built in firewall" I assume that you mean you have confirmed it is completely turned off. If that is not the case, double-check to make sure that it hasn't reverted to being active because it used to default to on but the policies from the domain controller turnd it off during connection (which will not happen now as the domain controller isn't there).

Not seeing its DC should not otherwise affect incoming connections. You could try dropping it from the domain and using local auth (or joining the domain the other machines are on) to verify this makes no difference.

Also, check to make sure the machine has a correct IP address. It may no it it used to get its address assigned via DHCP from the old DC. Not having a correct address would stop it making outgoing connections to other machines on the subnet too though.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .