Re: PC moved to another network still looking for a server on the previous

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: rudy (anonymous_at_discussions.microsoft.com)
Date: 06/10/04 

Date: Thu, 10 Jun 2004 12:21:32 -0700

I am replying to BM, he's the idiot on the internet
without virus protection.

He needs to goto Web 101

>-----Original Message-----
>Whom you are replying to?
>
>--
>Ramesh - Microsoft MVP
>Windows XP Shell/User
>http://www.mvps.org/sramesh2k
>
>AumHa VSOP: http://www.aumha.org
>
>"Rudy" <anonymous@discussions.microsoft.com> wrote in
message news:1a8fc01c44f1c$efdbbb10$a601280a@phx.gbl...
>Here's a better answer.
>
>Take your computer, turn it off, and throw it out in the
>garbage!
>
>Your an idiot being on the internet without virus
>protection...I would hate to see what your sex life is
>like.....
>
>
>>-----Original Message-----
>>Get TCPView from www.sysinternals.com and run it. Close
>all the internet based apps (for easier reading)
>>
>>Now, do what you did (right-click and icon?), See if
>there is any new entry in TCPView (indicated by green
>color) and note down the Process Name, Process ID. (say
>filename.exe:100 - 100 being the pid) and see the remote
>address in 192.xxx.xxx.xxx range.
>>
>>To know more about that application/process:
>>(are you there DavidC ? ;) )
>>
>>If you have Pro, Type
>>tasklist /m /fi "imagename eq <processname you noted>"
>>c:\out.txt
>>
>>Now, open out.txt and note down the odd DLL (non-ms
DLLs).
>>
>>You can have a DLL lookup at:
>http://support.microsoft.com/servicedesks/fileversion/dlli
n
>fo.asp?fr=0&sd=msdn
>>
>>BTW, the above is to see if the problem is due to a
>shellextension. Might work, but no guarantee.
>>
>>--
>>Ramesh - Microsoft MVP
>>Windows XP Shell/User
>>http://www.mvps.org/sramesh2k
>>
>>AumHa VSOP: http://www.aumha.org
>>
>><bm@bm.bm> wrote in message
>news:OWVdybxTEHA.2704@TK2MSFTNGP10.phx.gbl...
>>I think it is a problem with windows as on my previous
>network I had address
>>192.168.10.250. Somewhere in Windows it still remembers
>that address
>>somehow.
>>
>>"Juan Pablo Barrios [uy]" <aaaaa@bbbb.ccc> wrote in
>message
>>news:O2wT2QxTEHA.3988@tk2msftngp13.phx.gbl...
>>> Do you have an updated antivirus running?
>>> Did you check against possible spyware?
>>>
>>> I suspect that you have a malware in your computer.
>>>
>>> --
>>> Saludos
>>> Regards
>>> Juan Pablo.
>>> ***** Sigamos el tema en el grupo para beneficio de
>todos *****
>>> ***** Let's follow the subject in the group for
>everyone's benefit *****
>>> juanpbarrios.stress@hotmail.stress.com
>>> - Relájate antes de escribirme... ;-)
>>> - Relax before writing to me... ;-)
>>> --
>>> <bm@bm.bm> escribió en el mensaje
>>> news:uPL4DMxTEHA.1284@TK2MSFTNGP10.phx.gbl...
>>> > Hi,
>>> >
>>> > I have an anoying problem. When I right click a file
>it takes about 20
>>sec
>>> > for the context menu to appear. If I disable my
>network it works just
>>> fine.
>>> > So what I was able to track is that I click a right
>button over a file
>>> then
>>> > I could see using netstat that the PC is trying a
>conneciton to
>>> > 192.168.10.250 which does not ecxist on my network.
>It existed on the
>>> > previous but not any more.
>>> > For few seconds it tried to establish connection to
>192.168.10.250:445
>>> then
>>> > for few more seconds it tries 192.168.10.250:139
then
>192.168.10.250:80
>>> and
>>> > because such address does not exist after about of
20
>seconds it gives
>>up
>>> > and it shows the context menu. Thogh this is quite
>annoying. I couldn't
>>> find
>>> > the entry 192.168.10.250 in the registry neither in
>any file on my
>>system.
>>> > How the hell it decided to search exactly this
>address?!?!
>>> >
>>> > I tried disabling NWLink - no positive results.
>>> >
>>> > Any ideas how to overcome this problem without
>reinstall as I need 3
>>days
>>> to
>>> > make a full reinstall of the PC I use really a lot
of
>software.
>>> >
>>> > Any ideas will be appreciated as I already spend 1
>day.
>>
>>.
>>
>.
>

Quantcast