New server not reachable by other computers

Here's the peculiar thing. It's registered on AD, it can read network
folders on other computers, but no other computers can ping it or telnet into
it or otherwise recognize its existence.

I'm wondering if this has something to do with new server security settings
(only windows update is allowed to contact the computer), that it somehow
didn't turn this off once I finished with the updates.

If this be the case, how does one shut off this security setitng? Any other
ideas what might be causing this?

---------
Ron B.
www.es.tv

Hello Ron B.,

How is your network setup and which Operating system do you use?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Here's the peculiar thing. It's registered on AD, it can read network
> folders on other computers, but no other computers can ping it or
> telnet into it or otherwise recognize its existence.
>
> I'm wondering if this has something to do with new server security
> settings (only windows update is allowed to contact the computer),
> that it somehow didn't turn this off once I finished with the updates.
>
> If this be the case, how does one shut off this security setitng? Any
> other ideas what might be causing this?
>
> ---------
> Ron B.
> www.es.tv

Windows Server 2003 Standard R2. We just have a single domain sitting on a
Class C network and a router doing NAT.
The only peculiar thing is I've set up an ISA server acting as a second
possible gateway on the LAN. But this error persists no matter what default
gateway I connect the new server to. I don't think this would be the issue
anyway, it hasn't been so far.
---------
Ron B.
www.es.tv


"Meinolf Weber" wrote:

> Hello Ron B.,
>
> How is your network setup and which Operating system do you use?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>
> > Here's the peculiar thing. It's registered on AD, it can read network
> > folders on other computers, but no other computers can ping it or
> > telnet into it or otherwise recognize its existence.
> >
> > I'm wondering if this has something to do with new server security
> > settings (only windows update is allowed to contact the computer),
> > that it somehow didn't turn this off once I finished with the updates.
> >
> > If this be the case, how does one shut off this security setitng? Any
> > other ideas what might be causing this?
> >
> > ---------
> > Ron B.
> > www.es.tv
>
>
>

Hello Ron B.,

The point is the ISA server, it will block everything until you allow it.
I think better post it to microsoft.public.isa or microsoft.public.isa.configuration

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Windows Server 2003 Standard R2. We just have a single domain sitting
> on a
> Class C network and a router doing NAT.
> The only peculiar thing is I've set up an ISA server acting as a
> second
> possible gateway on the LAN. But this error persists no matter what
> default
> gateway I connect the new server to. I don't think this would be the
> issue
> anyway, it hasn't been so far.
> ---------
> Ron B.
> www.es.tv
> "Meinolf Weber" wrote:
>
>> Hello Ron B.,
>>
>> How is your network setup and which Operating system do you use?
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>>> Here's the peculiar thing. It's registered on AD, it can read
>>> network folders on other computers, but no other computers can ping
>>> it or telnet into it or otherwise recognize its existence.
>>>
>>> I'm wondering if this has something to do with new server security
>>> settings (only windows update is allowed to contact the computer),
>>> that it somehow didn't turn this off once I finished with the
>>> updates.
>>>
>>> If this be the case, how does one shut off this security setitng?
>>> Any other ideas what might be causing this?
>>>
>>> ---------
>>> Ron B.
>>> www.es.tv

I tried sending a LAN -> LAN rule to allow all traffic and that didn't work.
I also set up a rule to allow the LAN to ping this new server and that didn't
work either.

---------
Ron B.
mrbiggs.net


"Meinolf Weber" wrote:

> Hello Ron B.,
>
> The point is the ISA server, it will block everything until you allow it.
> I think better post it to microsoft.public.isa or microsoft.public.isa.configuration
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>
> > Windows Server 2003 Standard R2. We just have a single domain sitting
> > on a
> > Class C network and a router doing NAT.
> > The only peculiar thing is I've set up an ISA server acting as a
> > second
> > possible gateway on the LAN. But this error persists no matter what
> > default
> > gateway I connect the new server to. I don't think this would be the
> > issue
> > anyway, it hasn't been so far.
> > ---------
> > Ron B.
> > www.es.tv
> > "Meinolf Weber" wrote:
> >
> >> Hello Ron B.,
> >>
> >> How is your network setup and which Operating system do you use?
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >>> Here's the peculiar thing. It's registered on AD, it can read
> >>> network folders on other computers, but no other computers can ping
> >>> it or telnet into it or otherwise recognize its existence.
> >>>
> >>> I'm wondering if this has something to do with new server security
> >>> settings (only windows update is allowed to contact the computer),
> >>> that it somehow didn't turn this off once I finished with the
> >>> updates.
> >>>
> >>> If this be the case, how does one shut off this security setitng?
> >>> Any other ideas what might be causing this?
> >>>
> >>> ---------
> >>> Ron B.
> >>> www.es.tv
>
>
>

"Ron B." <(E-Mail Removed)> wrote in message
> Here's the peculiar thing. It's registered on AD, it can read network
> folders on other computers, but no other computers can ping it or telnet
> into
> it or otherwise recognize its existence.
>
> I'm wondering if this has something to do with new server security
> settings
> (only windows update is allowed to contact the computer), that it somehow
> didn't turn this off once I finished with the updates.
>
> If this be the case, how does one shut off this security setitng? Any
> other
> ideas what might be causing this?

Did you check to see if the Windows Firewall was enabled on the server and
blocking the traffic?

You can check by going to Network Connections in Control Panel, Right
Clicking your LAN connection, choosing properties and going to the Advanced
tab. Then click the Settings button to see if the Firewall is On or Off.

--Jeffrey

Yes, that did the trick, thanks. Apparently the OS had never disabled the
service when I first started it up and ran the updates.
--
---------
Ron B.
mrbiggs.net


"Jeffrey Tadlock" wrote:

> "Ron B." <(E-Mail Removed)> wrote in message
> > Here's the peculiar thing. It's registered on AD, it can read network
> > folders on other computers, but no other computers can ping it or telnet
> > into
> > it or otherwise recognize its existence.
> >
> > I'm wondering if this has something to do with new server security
> > settings
> > (only windows update is allowed to contact the computer), that it somehow
> > didn't turn this off once I finished with the updates.
> >
> > If this be the case, how does one shut off this security setitng? Any
> > other
> > ideas what might be causing this?
>
> Did you check to see if the Windows Firewall was enabled on the server and
> blocking the traffic?
>
> You can check by going to Network Connections in Control Panel, Right
> Clicking your LAN connection, choosing properties and going to the Advanced
> tab. Then click the Settings button to see if the Firewall is On or Off.
>
> --Jeffrey
>
>
>