Re: Strange behavior on one pc in SBS 2003 domain

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Windows firewall OFF generally means that some other firewall has replaced it. This could be an antivirus system or standalone software firewall. In normal condition the Windows Firewall on a system attached to SBS03 will be ON (and controlled by GPO).

The secret is, I believe, PING. If you can't ping you can't sing. The Windows Firewall on SBS clients, correctly getting policy, does not block ping (at least in the 'domain' setting, and I also believe the 'off domain'). The ISA FWC also _should not_ stop ping.

--
SBS remote support services. (Fees apply)
mickm at mickmalloy dot dyndns dot org
"BogiesToBirdies" <Birdies@xxxxxxxxxxxxxx> wrote in message news:evRuVwKtJHA.4876@xxxxxxxxxxxxxxxxxxxxxxx
Windows Firewall is turned off. ISA 2004 client is install and connected to the SBS / ISA server. I did what Dave suggested and still can't ping that machine.


"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message news:eQ1FDqJtJHA.1236@xxxxxxxxxxxxxxxxxxxxxxx
some sort of firewall on the PC?

--
SBS remote support services. (Fees apply)
mickm at mickmalloy dot dyndns dot org
"BogiesToBirdies" <Birdies@xxxxxxxxxxxxxx> wrote in message news:OBTzmkJtJHA.3988@xxxxxxxxxxxxxxxxxxxxxxx
I have an XP SP3 pc in my SBS 2003 SP2 Premium domain. The pc has a computer account and was able to successfully join the pc via the connectcomputer wizard. It has the ISA client loaded and has no issues accessing the internet or any other resource in the domain. The problem is accessing that pc in the doamin from my admin workstation or even from the server console. I cannot map a network drive \\computername\C$ or any other share. I cannot rdp to it even though remote desktop on the pc is enabled. I cannot even ping the pc. I've checked dns both forwarding zones and reverse and all is ok there. I'm lost as to why.
Reason I ask is that I have installed a new Symantec EndPoint server on a Windows 2008 server and cannot push the new client out to that pc even though I have no problems or issues pushing out to any other pc in the domain. I can see the pc and select it to have the new EndPoint client pushed however it comes back with a "network path not found" error. I've evn tried switching ports in the patch panel as well as switching wall jacks. Other than this the pc seems to be fine. Any clues or suggestions very much appreciated.





.

Relevant Pages

  • Re: Cannot Ping New Windows Server 2003 Machine from XP Client
    ... How to Enable File and Printer Sharing in Windows Firewall ... I disabled it and I can now ping the server and map shared drives. ... the server cannot "see" shared drives on my client PC ...
    (microsoft.public.windows.server.networking)
  • Re: Cant ping Windows 2003 Ent SP1 R2 server after R2 Upgrade
    ... Does this still hold true even if the Windows Firewall is completely ... The other server ... You just can't ping them. ... ok now" but then as it carries on loading (final stages before ...
    (microsoft.public.windows.server.networking)
  • Re: Can not access server remotely
    ... Check the Windows Firewall. ... boxes to allow ICMP reply (ping) and RDP? ... > I just installed service pack 1 on my windows 2003 server and now I ... > As soon as I uninstall service pack 1 I can both ping and Remote ...
    (microsoft.public.windows.server.networking)
  • Re: Can not access server remotely
    ... > When I click on Windows Firewall I am getting the following error ... > The boxes to allow ICMP reply (ping) and RDP are checked. ... >>> I just installed service pack 1 on my windows 2003 server and now I ... >>> As soon as I uninstall service pack 1 I can both ping and Remote ...
    (microsoft.public.windows.server.networking)
  • Re: Remote Desktop/Networking
    ... utility is known for blocking network traffic, ... I don't know if I'm correct but I think once the ping ... is resolved the remote desktop should work. ... Turn off the Windows firewall during testing until you get your ...
    (microsoft.public.windowsxp.general)