From: "Thees Peereboom" 

Geo,

On JohnB's request I changed the IP of that machine - makes no difference...

- Thees Peereboom

On Wed, 18 Aug 2004 18:32:57 -0400, Geo.  wrote:

> Ok but I can explain that, the firewall can block based on IP address so
> it can
> block just one machine and not the others. It can also be that the IP
> changed
> during the 3 weeks or that something tried to get to that IP and set off
> the
> firewall and you just clicked on a popup, I've done that, locked my own
> machines out because the stupid firewall does a popup while I'm typing.
>
> Geo.
>
> "Thees Peereboom"  wrote in message
> news:opscw004vj2hvhrx{at}news.barkto.com...
>> Geo,
>>
>> There's only one firewall, in winproxy. There are also two arguments
>> against a firewallissue:
>> - other machines have access
>> - it happened suddenly, after the machine was switched on after three
>> weeks of inactivity.
>>
>> - Thees Peereboom
>>
>> On Tue, 17 Aug 2004 18:18:49 -0400, Geo.  wrote:
>>
>> > "Thees Peereboom"  wrote in message
>> > news:opscv5q5b02hvhrx{at}news.barkto.com...
>> >
>> >> WS1 can also ping WS3 (tried that before) and 4.2.2.2
'request timed
>> >> out'
>> >
>> > If you can ping I'm still betting on it being a firewall issue on
>> either
>> > WS1 or
>> > WS3. Can you try disabling the two firewalls just for a short test to
>> > see if
>> > nslookup works correctly with the firewalls off?
>> >
>> > Geo.
>> >
>> >
>>
>
>

--- BBBS/NT v4.01 Flag-5