From: "Thees Peereboom" 

Bob,

I thought of that, too, but unfortunately it refuses to let itself delete...

Met vriendelijke groet,

Thees Peereboom
Independent IT Adviser for advertising and media organisations

t +31 (0)20 647 8950
f +31 (0)20 647 3198
e theesp{at}peereboom.nl



On Mon, 16 Aug 2004 07:14:21 -0400, Robert Comer
 wrote:

> I've seen Win2K do this and the easiest way to fix it has been to delete
> the
> LAN network connection and recreate it.
>
> - Bob Comer
>
>
> "Thees Peereboom"  wrote in message
> news:opscth36iy2hvhrx{at}news.barkto.com...
>> John,
>>
>> Thanks for replying - see attached screendump.
>>
>> For some reason I seem able to browse the internal network but unable to
>> browse the internet.
>>
>> TIA,
>>
>> - Thees Peereboom
>>
>> On Sun, 15 Aug 2004 12:53:46 GMT, John Beckett
>>  wrote:
>>
>>> "Thees Peereboom"  wrote in message
>>> news::
>>>> VNC, however, doesn't work, claiming a
>>>> socket-error ('cannot create socket').
>>>
>>> It doesn't sound likely from your description, but one worry with VNC
>>> is
>>> that if a trojan had installed a VNC-like program on the computer,
>>> there
>>> is a possibility that the first would interfere with the second.
>>>
>>> Consider running the following at command prompt:
>>> netstat -n >n.txt
>>> n.txt
>>>
>>>> I get a  DNSerror.
>>>
>>> At command prompt on the problem computer, what happens with this:
>>> ping cisco.com
>>>
>>> The ping may fail (timeout). But does it show the IP of cisco.com? What
>>> happens on other computer when you try this?
>>>
>>> John
>>>
>>
>>
>
>

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