Can't Firewall/Remote

[Kevin A]

I used to be able to remote desktop into my XP machine, now I can't. It
seems SP2 has screwed something up. I'm assuming that if you aren't running
the firewall services, then all incoming ports are disabled by default? The
firewall service won't start and I've followed several posts that I googled.
None of those seemed to work. From resetting winsock to deleting a reg
entry and letting it reset.

Any suggestions to getting RD running again? Or, if it is the firewall,
getting that running again? When I try to manually start it, it complains
about a DB error.

Please advise.

 

[Steven L Umbach]

If the Windows Firewall is not running then all ports used on the computer
are available to the network. Double check that RDP is enabled in Control
Panel/system/remote and use the command netstat -an to verify that port 3389
TCP is listening on local address as shown in the example below from my
computer. Of course I would not want it running anyhow if I had no firewall
protecting my computer from the internet. If you have an internet router
also then you would be protected from the internet even if the Windows
Firewall was disabled. You might want to try System Restore
[programs\accessories\system tools\system restore]to restore your computer
to a point before your problems began if you have one and be sure to scan
your computer for malware since malware is a common cause of problems with
the Windows Firewall. Beyond that you may need to look at doing a repair
install of your operating system as described in the link below being sure
to read the entire article but I would not attempt that unless you have made
attempts to clean your computer of detected malware and spyware. --- Steve

http://www.michaelstevenstech.com/XPrepairinstall.htm
http://www.microsoft.com/athome/security/protect/windowsxpsp2/Default.mspx
-- Protect Your PC tips and links to dealing with malware and spyware.

D:\WINDOWS\system32>netstat -an

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1025 0.0.0.0:0 LISTENING
TCP 192.168.1.52:139 0.0.0.0:0 LISTENING
TCP 192.168.1.52:1102 192.168.1.251:3389 ESTABLISHED
TCP 192.168.1.52:1436 216.196.97.136:119 ESTABLISHED

 

[Kevin A]

Considering my firewall is disabled and that all the ports should be
available at that time, and considering that I actually can't even ping it
on the local subnet, that tells me something else is screwy. Maybe the
repair is the right direction.

I already scanned for malware and viruses, nothing surfaced.

I'll give that a try.

If the Windows Firewall is not running then all ports used on the computer
are available to the network. Double check that RDP is enabled in Control
Panel/system/remote and use the command netstat -an to verify that port
3389 TCP is listening on local address as shown in the example below from
my computer. Of course I would not want it running anyhow if I had no
firewall protecting my computer from the internet. If you have an internet
router also then you would be protected from the internet even if the
Windows Firewall was disabled. You might want to try System Restore
[programs\accessories\system tools\system restore]to restore your computer
to a point before your problems began if you have one and be sure to scan
your computer for malware since malware is a common cause of problems with
the Windows Firewall. Beyond that you may need to look at doing a repair
install of your operating system as described in the link below being sure
to read the entire article but I would not attempt that unless you have
made attempts to clean your computer of detected malware and spyware. ---
Steve

http://www.michaelstevenstech.com/XPrepairinstall.htm

tp://www.microsoft.com/athome/security/protect/windowsxpsp2/Default.mspx
-- Protect Your PC tips and links to dealing with malware and spyware.

D:\WINDOWS\system32>netstat -an

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1025 0.0.0.0:0 LISTENING
TCP 192.168.1.52:139 0.0.0.0:0 LISTENING
TCP 192.168.1.52:1102 192.168.1.251:3389 ESTABLISHED
TCP 192.168.1.52:1436 216.196.97.136:119 ESTABLISHED

I used to be able to remote desktop into my XP machine, now I can't. It
seems SP2 has screwed something up. I'm assuming that if you aren't
running
the firewall services, then all incoming ports are disabled by default?
The
firewall service won't start and I've followed several posts that I
googled.
None of those seemed to work. From resetting winsock to deleting a reg
entry and letting it reset.

Any suggestions to getting RD running again? Or, if it is the firewall,
getting that running again? When I try to manually start it, it
complains
about a DB error.

Please advise.

 

[Steven L Umbach]

Do you happen to have any other software installed that may be doing IP
filtering? Sometimes even antivirus programs have something that is called
worm protection that will block inbound connections. Assuming it does not
put your computer at risk try booting into Safe Mode with networking to see
if that makes any difference as that will bypass such programs since they
will not start in Safe Mode but then the Windows Firewall might. Try doing
some basic network troubleshooting such as try pinging your computer by IP
address also instead of name, running the command ipconfig /all to make sure
the computer does have an available network adapter with an IP address and
for the network you expect, and try pinging localhost, 127.0.0.1, and the IP
address shown with ipconfig /all to see if any or all work. --- Steve

Considering my firewall is disabled and that all the ports should be
available at that time, and considering that I actually can't even ping it
on the local subnet, that tells me something else is screwy. Maybe the
repair is the right direction.

I already scanned for malware and viruses, nothing surfaced.

I'll give that a try.

If the Windows Firewall is not running then all ports used on the
computer are available to the network. Double check that RDP is enabled
in Control Panel/system/remote and use the command netstat -an to verify
that port 3389 TCP is listening on local address as shown in the example
below from my computer. Of course I would not want it running anyhow if I
had no firewall protecting my computer from the internet. If you have an
internet router also then you would be protected from the internet even
if the Windows Firewall was disabled. You might want to try System
Restore [programs\accessories\system tools\system restore]to restore your
computer to a point before your problems began if you have one and be
sure to scan your computer for malware since malware is a common cause of
problems with the Windows Firewall. Beyond that you may need to look at
doing a repair install of your operating system as described in the link
below being sure to read the entire article but I would not attempt that
unless you have made attempts to clean your computer of detected malware
and spyware. --- Steve

http://www.michaelstevenstech.com/XPrepairinstall.htm


://www.microsoft.com/athome/security/protect/windowsxpsp2/Default.mspx
-- Protect Your PC tips and links to dealing with malware and spyware.

D:\WINDOWS\system32>netstat -an

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1025 0.0.0.0:0 LISTENING
TCP 192.168.1.52:139 0.0.0.0:0 LISTENING
TCP 192.168.1.52:1102 192.168.1.251:3389 ESTABLISHED
TCP 192.168.1.52:1436 216.196.97.136:119 ESTABLISHED

I used to be able to remote desktop into my XP machine, now I can't. It
seems SP2 has screwed something up. I'm assuming that if you aren't
running
the firewall services, then all incoming ports are disabled by default?
The
firewall service won't start and I've followed several posts that I
googled.
None of those seemed to work. From resetting winsock to deleting a reg
entry and letting it reset.

Any suggestions to getting RD running again? Or, if it is the firewall,
getting that running again? When I try to manually start it, it
complains
about a DB error.

Please advise.