Networking with XP pro

C

Chuck

Chuck,
i disabled the firewalls, started the computer in "safe mode".

in safe mode i was able to ping the computers. from both sides

when logging back into windows. I couldnt ping anything

"New kid on the block" wrote:

That's a good start. If Safe Mode gives you ping connectivity, then look at the
difference between Safe Mode and Normal Mode.

Get PSList (free) from <http://www.sysinternals.com/ntw2k/freeware/pslist.shtml>
Run it as "pslist >c:\pslist.txt". Print out c:\pslist.txt from Notepad.
Compare pslist from Normal and Safe modes, line for line, on both computers.
The answer will be there.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
G

Guest

chuck, I installed pslist but i cant get it to run. i click on the file and
the cmd promd pops up a nano second and is gone....any insite?
 
C

Chuck

chuck, I installed pslist but i cant get it to run. i click on the file and
the cmd promd pops up a nano second and is gone....any insite?

Open a command window. Start - Run - "cmd". CD to the folder where you
installed pslist. Type "pslist /?" for details.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
G

Guest

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jason>pslist /?
'pslist' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Jason>pslist/?
'pslist' is not recognized as an internal or external command,
operable program or batch file.

this is the message i get
 
G

Guest

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jason>pslist
'pslist' is not recognized as an internal or external command,
operable program or batch file.
 
G

Guest

chuck i can ping ip for compaqfront1 (192.168.1.101) from dellfront1
(192.168.1.1)
but, it will not ping the name of the computer (compaqfront1) gives the
following message in "

"Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jason>ping compaqfront1
Ping request could not find host compaqfront1. Please check the name and try
aga
in."

The compaqfront1 can ping the ip of dellfront1(192.168.1.1) but will not
ping the name of the computer
 
C

Chuck

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jason>pslist
'pslist' is not recognized as an internal or external command,
operable program or batch file.

What folder did you copy pslist to? You have to be positioned in that folder.

Or a better alternative:
1) Create a new folder, say "C:\Utility".
2) Copy PSList to C:\Utility.
3) Add "C:\Utility" to the system Path. Control Panel - System - Advanced tab
- Environment Variables - Under System variables, add ";C:\Utility" to the END
of the Path variable (highlight Path and click Edit).

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
C

Chuck

chuck i can ping ip for compaqfront1 (192.168.1.101) from dellfront1
(192.168.1.1)
but, it will not ping the name of the computer (compaqfront1) gives the
following message in "

"Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jason>ping compaqfront1
Ping request could not find host compaqfront1. Please check the name and try
aga
in."

The compaqfront1 can ping the ip of dellfront1(192.168.1.1) but will not
ping the name of the computer

Can you ping BOTH compaqfront1 from dellfront1, AND dellfront1 from
compaqfront1, by ip address? If not, please rerun tping, copy, and paste ENTIRE
tping.txt from both computers into your next post. I need a precise statement
of what isn't working.

The ping command is a pretty basic component of TCP/IP networking in all
operating systems. For ping by ip address to work, you need:
- Physical connectivity (cables connect each computer).
- Network connectivity (TCP/IP).
- Network configuration (ipconfig is good here).
- No firewalls interfering.

Looking at the ipconfigs, they look normal. Node types "Unknown" (CompaqFront1)
and "Hybrid" (DellFront1) are compatible.

If you can ping one computer from the other, by ip address, you have
connectivity, and configuration. The file sharing problem, "...not accessible /
no permissions...", and the "ping request could not find host..." indicate a
problem with name resolution. Node types are normal, so any problem with name
resolution has to be a misconfigured firewall.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
G

Guest

When i ran from the website...i first put the program onto desktop

but i moved to Program files..... utility folder

but it still wont work..



Chuck said:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jason>pslist
'pslist' is not recognized as an internal or external command,
operable program or batch file.

What folder did you copy pslist to? You have to be positioned in that folder.

Or a better alternative:
1) Create a new folder, say "C:\Utility".
2) Copy PSList to C:\Utility.
3) Add "C:\Utility" to the system Path. Control Panel - System - Advanced tab
- Environment Variables - Under System variables, add ";C:\Utility" to the END
of the Path variable (highlight Path and click Edit).

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
C

Chuck

When i ran from the website...i first put the program onto desktop

but i moved to Program files..... utility folder

but it still wont work..

Please define "wont work". What error are you getting? Is the folder (what
exact folder name?) in the Path? Did you CD to that folder before running
pslist?
- Start a command window (Start - Run - "cmd").
- "cd \program files\utility "
- "pslist"

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
G

Guest

well......i just noticed that the IP has changed on compaqfront1? its
192.168.1.100
it was 192.168.1.101

i am confused.......anyway here is the tping for both

Pings from DELLFRONT1

Pinging COMPAQFRONT1
Ping request could not find host COMPAQFRONT1. Please check the name and try
again.


Pinging 192.168.1.101


Pinging 192.168.1.101 with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pinging DELLFRONT1


Pinging DELLFRONT1 [192.168.1.101] with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pinging 192.168.1.100


Pinging 192.168.1.100 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Pinging 192.168.1.1


Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pinging 127.0.0.1


Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pings from COMPAQFRONT1

Pinging COMPAQFRONT1


Pinging COMPAQFRONT1 [192.168.1.100] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Pinging 192.168.1.101


Pinging 192.168.1.101 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Pinging DELLFRONT1
Ping request could not find host DELLFRONT1. Please check the name and try
again.


Pinging 192.168.1.100


Pinging 192.168.1.100 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Pinging 192.168.1.1


Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time=11ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 11ms, Average = 2ms


Pinging 127.0.0.1


Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms



Chuck said:
chuck i can ping ip for compaqfront1 (192.168.1.101) from dellfront1
(192.168.1.1)
but, it will not ping the name of the computer (compaqfront1) gives the
following message in "

"Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jason>ping compaqfront1
Ping request could not find host compaqfront1. Please check the name and try
aga
in."

The compaqfront1 can ping the ip of dellfront1(192.168.1.1) but will not
ping the name of the computer

Can you ping BOTH compaqfront1 from dellfront1, AND dellfront1 from
compaqfront1, by ip address? If not, please rerun tping, copy, and paste ENTIRE
tping.txt from both computers into your next post. I need a precise statement
of what isn't working.

The ping command is a pretty basic component of TCP/IP networking in all
operating systems. For ping by ip address to work, you need:
- Physical connectivity (cables connect each computer).
- Network connectivity (TCP/IP).
- Network configuration (ipconfig is good here).
- No firewalls interfering.

Looking at the ipconfigs, they look normal. Node types "Unknown" (CompaqFront1)
and "Hybrid" (DellFront1) are compatible.

If you can ping one computer from the other, by ip address, you have
connectivity, and configuration. The file sharing problem, "...not accessible /
no permissions...", and the "ping request could not find host..." indicate a
problem with name resolution. Node types are normal, so any problem with name
resolution has to be a misconfigured firewall.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
G

Guest

i noticed that dellfront1 and compaqfront1 have changed ip
addresses.......should i still configure to obtain IP automatic?

New kid on the block said:
well......i just noticed that the IP has changed on compaqfront1? its
192.168.1.100
it was 192.168.1.101

i am confused.......anyway here is the tping for both

Pings from DELLFRONT1

Pinging COMPAQFRONT1
Ping request could not find host COMPAQFRONT1. Please check the name and try
again.


Pinging 192.168.1.101


Pinging 192.168.1.101 with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pinging DELLFRONT1


Pinging DELLFRONT1 [192.168.1.101] with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pinging 192.168.1.100


Pinging 192.168.1.100 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Pinging 192.168.1.1


Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pinging 127.0.0.1


Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pings from COMPAQFRONT1

Pinging COMPAQFRONT1


Pinging COMPAQFRONT1 [192.168.1.100] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Pinging 192.168.1.101


Pinging 192.168.1.101 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Pinging DELLFRONT1
Ping request could not find host DELLFRONT1. Please check the name and try
again.


Pinging 192.168.1.100


Pinging 192.168.1.100 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Pinging 192.168.1.1


Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time=11ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255

Reply from 192.168.1.1: bytes=32 time<1ms TTL=255



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 11ms, Average = 2ms


Pinging 127.0.0.1


Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms



Chuck said:
chuck i can ping ip for compaqfront1 (192.168.1.101) from dellfront1
(192.168.1.1)
but, it will not ping the name of the computer (compaqfront1) gives the
following message in "

"Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jason>ping compaqfront1
Ping request could not find host compaqfront1. Please check the name and try
aga
in."

The compaqfront1 can ping the ip of dellfront1(192.168.1.1) but will not
ping the name of the computer

Can you ping BOTH compaqfront1 from dellfront1, AND dellfront1 from
compaqfront1, by ip address? If not, please rerun tping, copy, and paste ENTIRE
tping.txt from both computers into your next post. I need a precise statement
of what isn't working.

The ping command is a pretty basic component of TCP/IP networking in all
operating systems. For ping by ip address to work, you need:
- Physical connectivity (cables connect each computer).
- Network connectivity (TCP/IP).
- Network configuration (ipconfig is good here).
- No firewalls interfering.

Looking at the ipconfigs, they look normal. Node types "Unknown" (CompaqFront1)
and "Hybrid" (DellFront1) are compatible.

If you can ping one computer from the other, by ip address, you have
connectivity, and configuration. The file sharing problem, "...not accessible /
no permissions...", and the "ping request could not find host..." indicate a
problem with name resolution. Node types are normal, so any problem with name
resolution has to be a misconfigured firewall.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
G

Guest

ok i finally got pslist to work


sList 1.26 - Process Information Lister
Copyright (C) 1999-2004 Mark Russinovich
Sysinternals - www.sysinternals.com

Process information for DELLFRONT1:

Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time
Idle 0 0 2 0 0 0:49:06.546 0:00:00.000
System 4 8 70 313 0 0:00:07.562 0:00:00.000
SMSS 596 11 3 19 164 0:00:00.046 0:25:52.703
CSRSS 644 13 11 586 1736 0:00:03.609 0:25:51.562
WINLOGON 668 13 19 513 6580 0:00:01.984 0:25:51.312
SERVICES 712 9 15 290 1896 0:00:02.718 0:25:51.171
LSASS 724 9 19 355 5648 0:00:01.015 0:25:51.140
SVCHOST 900 8 5 134 1304 0:00:00.156 0:25:50.578
SVCHOST 968 8 13 454 5284 0:00:00.593 0:25:50.343
SVCHOST 1124 8 70 1519 17864 0:00:02.375 0:25:50.203
SVCHOST 1172 8 9 110 3292 0:00:00.531 0:25:50.156
SVCHOST 1336 8 18 302 9264 0:00:00.671 0:25:50.046
SPOOLSV 1500 8 12 159 3296 0:00:00.140 0:25:49.359
mcvsrte 1848 8 4 113 4896 0:00:00.328 0:25:41.671
MpfService 1876 8 9 143 3644 0:00:00.109 0:25:41.640
SVCHOST 136 8 5 129 2472 0:00:22.765 0:25:40.875
wdfmgr 244 8 4 67 1464 0:00:00.031 0:25:40.703
EXPLORER 424 8 27 775 35540 0:00:23.843 0:25:37.921
McShield 1032 13 16 125 5644 0:00:39.546 0:25:36.250
ALG 1368 8 9 119 3120 0:00:00.078 0:25:33.406
MpfAgent 1356 8 3 141 3756 0:00:00.078 0:25:33.343
hkcmd 1448 8 2 95 1556 0:00:00.406 0:25:33.140
jusched 1560 8 1 24 440 0:00:00.031 0:25:32.906
IntelMEM 1596 8 2 25 1016 0:00:00.031 0:25:32.703
PCMService 1588 8 13 323 8988 0:00:01.125 0:25:32.609
DVDLauncher 1636 8 2 40 688 0:00:00.046 0:25:32.484
realplay 1744 8 7 78 3936 0:00:00.500 0:25:32.312
mcagent 1984 8 2 158 4040 0:00:00.265 0:25:31.859
mmtask 280 8 3 73 628 0:00:00.031 0:25:31.562
mm_tray 348 8 1 37 1156 0:00:00.062 0:25:31.484
mcvsshld 444 8 2 138 2564 0:00:00.171 0:25:31.203
McVSEscn 716 8 2 122 2608 0:00:00.109 0:25:31.015
MpfTray 784 8 9 261 7836 0:00:12.296 0:25:30.656
RUNDLL32 1376 8 2 67 2332 0:00:00.078 0:25:29.828
CMESys 2028 8 17 262 6052 0:00:01.765 0:25:29.484
mscifapp 2096 8 6 105 2584 0:00:06.703 0:25:28.968
DSAgnt 2176 6 2 57 852 0:00:00.078 0:25:27.968
MSMSGS 2296 8 14 370 5776 0:00:00.328 0:25:26.953
wwDisp 2384 8 6 158 7852 0:00:00.250 0:25:26.062
mmod 2452 8 6 213 10976 0:00:00.734 0:25:23.453
SVCHOST 2472 8 8 95 1484 0:00:00.031 0:25:23.406
GMT 3388 8 21 350 13752 0:00:05.406 0:25:13.046
qbupdate 3492 8 4 194 3636 0:00:00.109 0:25:11.125
mcvsftsn 3872 8 4 161 2820 0:00:00.125 0:25:03.421
IEXPLORE 3784 8 21 640 20436 0:00:31.000 0:24:11.703
CMD 4088 8 1 32 1888 0:00:00.031 0:01:38.328
pslist 2320 13 2 82 724 0:00:00.046 0:00:00.093


PsList 1.26 - Process Information Lister
Copyright (C) 1999-2004 Mark Russinovich
Sysinternals - www.sysinternals.com

Process information for COMPAQFRONT1:

Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time
Idle 0 0 1 0 0 0:57:36.625 0:00:00.000
System 4 8 57 278 0 0:00:12.546 0:00:00.000
smss 572 11 3 21 164 0:00:00.031 1:03:53.531
csrss 648 13 11 559 1844 0:00:12.078 1:03:49.187
winlogon 672 13 20 594 9880 0:00:06.390 1:03:48.546
services 716 9 15 303 2104 0:00:04.031 1:03:47.796
lsass 728 9 20 361 3788 0:00:02.343 1:03:47.750
svchost 884 8 17 214 3224 0:00:00.328 1:03:46.968
svchost 952 8 10 375 1952 0:00:00.656 1:03:46.437
svchost 1048 8 81 1618 15972 0:00:08.437 1:03:46.312
svchost 1120 8 4 76 1320 0:00:00.171 1:03:46.203
svchost 1244 8 15 208 1856 0:00:00.171 1:03:45.093
spoolsv 1420 8 13 175 10104 0:00:18.687 1:03:44.687
scardsvr 1468 8 4 55 948 0:00:00.062 1:03:44.578
ccEvtMgr 1536 8 19 350 5284 0:00:10.859 1:03:44.390
compaq-rba 1552 8 11 236 4308 0:00:11.171 1:03:44.343
Navapsvc 1672 8 9 110 3264 0:00:01.609 1:03:43.671
NISUM 1712 8 5 117 1244 0:00:00.281 1:03:43.578
nvsvc32 1860 8 3 47 628 0:00:00.109 1:03:42.828
pctspk 1904 8 4 39 884 0:00:00.031 1:03:42.593
svchost 224 8 9 153 3300 0:00:00.421 1:03:41.125
wdfmgr 304 8 4 65 1596 0:00:00.015 1:03:40.265
CCPXYSVC 424 8 11 239 5104 0:00:10.796 1:03:39.734
alg 1192 8 5 103 1176 0:00:00.062 1:03:36.531
explorer 1000 8 17 504 17776 0:00:22.421 1:03:25.531
wscntfy 1008 8 1 30 604 0:00:00.078 1:03:25.296
SMTray 176 8 1 23 1192 0:00:00.109 1:03:15.765
LVComS 1632 8 2 94 2132 0:00:00.125 1:03:15.359
CCAPP 2276 8 30 517 9632 0:00:07.968 1:03:08.843
essspk 2352 8 2 31 876 0:00:00.046 1:03:04.984
realsched 2360 8 4 104 988 0:00:00.109 1:03:03.078
msmsgs 2432 8 9 338 3308 0:00:00.937 1:03:01.890
hpotdd01 2520 8 3 80 1320 0:00:00.562 1:02:56.875
WkCalRem 2556 8 2 26 484 0:00:00.078 1:02:55.578
hposol08 2568 8 4 178 3248 0:00:19.406 1:02:54.781
qbupdate 2632 8 6 211 3840 0:00:22.546 1:02:51.140
hpoevm08 2784 8 8 137 1312 0:00:06.140 1:02:40.500
HPZipm12 2984 8 2 55 812 0:00:00.343 1:02:33.828
hposts08 3156 8 3 139 3148 0:00:01.828 1:01:47.671
cmd 3208 8 1 32 2044 0:00:00.140 1:01:37.406
EXCEL 3880 8 5 256 6060 0:00:02.734 0:08:19.421
wmiprvse 3072 8 6 142 2436 0:00:00.156 0:01:13.937
pslist 1348 13 2 72 820 0:00:00.109 0:00:00.125
 
G

Guest

pslist for safe modes......also i resolved my IP issue..........i had to
restart the router

PsList 1.26 - Process Information Lister
Copyright (C) 1999-2004 Mark Russinovich
Sysinternals - www.sysinternals.com

Process information for DELLFRONT1:

Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time
Idle 0 0 2 0 0 0:02:37.953 0:00:00.000
System 4 8 46 218 0 0:00:02.812 0:00:00.000
SMSS 516 11 3 21 164 0:00:00.171 0:01:17.578
CSRSS 564 13 11 247 1676 0:00:00.640 0:01:14.906
WINLOGON 588 13 20 254 3408 0:00:00.562 0:01:14.218
SERVICES 632 9 15 236 1812 0:00:00.296 0:01:12.203
LSASS 644 9 20 283 2100 0:00:00.203 0:01:11.937
SVCHOST 808 8 18 193 2836 0:00:00.093 0:01:09.781
SVCHOST 876 8 13 248 5024 0:00:00.187 0:01:09.046
SVCHOST 1088 8 35 497 10336 0:00:00.125 0:01:08.140
SVCHOST 1104 8 5 57 1040 0:00:00.046 0:01:07.984
SVCHOST 1248 8 3 102 2444 0:00:00.046 0:01:07.421
EXPLORER 1824 8 9 245 6108 0:00:02.250 0:00:53.250
CMD 1952 8 1 32 1876 0:00:00.062 0:00:41.062
pslist 2008 13 2 82 680 0:00:00.031 0:00:00.281



PsList 1.26 - Process Information Lister
Copyright (C) 1999-2004 Mark Russinovich
Sysinternals - www.sysinternals.com

Process information for COMPAQFRONT1:

Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time
Idle 0 0 1 0 0 0:12:31.812 0:00:00.000
System 4 8 43 229 0 0:00:02.562 0:00:00.000
smss 504 11 3 21 164 0:00:00.203 0:12:41.250
csrss 568 13 10 219 1752 0:00:01.500 0:12:36.484
winlogon 592 13 14 228 4060 0:00:01.468 0:12:34.218
services 636 9 15 236 1984 0:00:00.718 0:12:30.703
lsass 648 9 13 264 2012 0:00:00.750 0:12:30.515
svchost 804 8 16 187 2976 0:00:00.093 0:12:26.968
svchost 892 8 9 184 1684 0:00:00.125 0:12:26.078
svchost 1012 8 29 636 8920 0:00:00.687 0:12:25.546
svchost 1072 8 4 54 1156 0:00:00.062 0:12:25.390
svchost 1200 8 3 75 1188 0:00:00.078 0:12:24.578
explorer 1628 8 10 266 9536 0:00:04.796 0:12:09.734
cmd 2020 8 1 32 2032 0:00:00.062 0:00:34.281
 
P

Paul

You seem a good and friendly expert on this area. I am trying to
follow your advice in a similar problem: two XP pro's linked directly
together. One of the 2 PC's can ping the other but not the other way
around. When I switch the one that can see the other to safe mode,
entworking is fine. I ran PSLIST and looked at the differences but
couldn't find any obvious things. Then I tried to shut down all the
processes that were present on a normal login but not on a safe mode
login. At some stage, the computer shut down because I was closing
down too many processes.

Here are the lines PSLIST reports for safe mode login:
Process information for KIDSPC:

Name Pid Pri Thd Hnd Priv CPU Time Elapsed
Time
Idle 0 0 1 0 0 0:02:25.278
0:00:00.000
System 4 8 46 221 0 0:00:09.453
0:00:00.000
smss 260 11 3 21 164 0:00:00.270
0:02:54.410
csrss 316 13 11 247 1836 0:00:05.127
0:02:47.560
winlogon 340 13 20 243 4532 0:00:01.331
0:02:43.164
services 384 9 16 238 2008 0:00:00.510
0:02:36.304
lsass 396 9 18 272 2188 0:00:08.582
0:02:35.743
svchost 548 8 22 204 2736 0:00:00.100
0:02:27.642
svchost 624 8 9 181 1684 0:00:00.220
0:02:25.028
svchost 696 8 36 654 9388 0:00:00.921
0:02:23.586
svchost 708 8 4 54 1152 0:00:00.060
0:02:23.326
svchost 772 8 3 75 1184 0:00:00.080
0:02:22.374
explorer 1124 8 10 290 11480 0:00:14.140
0:01:56.557
cmd 1436 8 1 32 2028 0:00:00.070
0:00:24.385
pslist 1448 13 2 70 800 0:00:00.070
0:00:00.290

and here for the normal login:
Process information for KIDSPC:

Name Pid Pri Thd Hnd Priv CPU Time Elapsed
Time
Idle 0 0 1 0 0 0:20:36.397
0:00:00.000
System 4 8 52 288 0 0:00:10.695
0:00:00.000
smss 308 11 3 21 164 0:00:00.040
0:21:22.484
csrss 356 13 12 369 1920 0:00:02.763
0:21:19.840
winlogon 380 13 20 443 6276 0:00:03.044
0:21:18.418
services 424 9 17 279 2100 0:00:03.454
0:21:18.117
lsass 436 9 22 329 3732 0:00:16.413
0:21:18.067
svchost 588 8 20 206 2756 0:00:00.280
0:21:16.815
svchost 632 8 10 222 1768 0:00:00.340
0:21:16.365
svchost 668 8 73 1258 11792 0:00:04.025
0:21:16.215
svchost 712 8 5 72 1284 0:00:00.090
0:21:16.094
svchost 752 8 6 128 1584 0:00:00.080
0:21:15.223
spoolsv 912 8 15 155 3308 0:00:00.200
0:21:13.361
SAgent2 1044 8 10 80 1384 0:00:00.050
0:21:05.980
tcpsvcs 1192 8 2 74 1160 0:00:00.090
0:21:05.629
snmp 1220 8 5 155 1404 0:00:00.100
0:21:05.499
svchost 1260 8 5 131 2456 0:00:00.220
0:21:05.459
alg 1580 8 6 104 1192 0:00:00.060
0:21:01.554
wscntfy 228 8 1 29 620 0:00:00.040
0:01:54.274
explorer 552 8 12 324 10480 0:00:10.024
0:01:52.982
WCESCOMM 820 8 2 64 1168 0:00:00.030
0:01:31.100
rundll32 584 8 2 56 10224 0:00:00.981
0:01:18.492
cmd 1424 8 1 32 2044 0:00:00.080
0:01:17.271
pslist 852 13 2 70 812 0:00:00.030
0:00:00.160

Could you advise on what could cause the difference? I am trying to
figure it out for good after several trials that obviously weren't
successful. I always though it was my other machine causing the
problem because that is connected to internet and thus uses firewalls.
Hope you can help me.

thanX

Paul

ps: I also did a ipconfig /all on this machine at normal login (it is
in Dutch I am sorry)

Windows IP-configuratie



Host-naam . . . . . . . . . . . .: KIDSPC

Primair DNS-achtervoegsel. . . . .:

Knooppunttype . . . . . . . . . . : gemengd

IP-routering ingeschakeld. . . . .: nee

WINS-proxy ingeschakeld . . . . . : nee

DNS-achtervoegselzoeklijst. . . . : mshome.net



Ethernet-adapter LAN-verbinding 4:



Verbindingsspec. DNS-achtervoegsel: mshome.net

Beschrijving . . . . . . . . . . .:

Realtek RTL8139 Family PCI Fast Ethernet NIC

Fysiek adres. . . . . . . . . . . : 00-40-F4-6E-FA-18

DHCP ingeshakeld. . . . . . . . . : ja

Autom. configuratie ingeschakeld. : ja

IP-adres. . . . . . . . . . . . . : 192.168.0.206

Subnetmasker. . . . . . . . . . . : 255.255.255.0

Standaardgateway. . . . . . . . . : 192.168.0.1

DHCP-server . . . . . . . . . . . : 192.168.0.1

DNS-servers . . . . . . . . . . . : 192.168.0.1

Lease verkregen . . . . . . . . . : dinsdag 9 november 2004
22:22:07

Lease verlopen . . . . . . . . . : dinsdag 16 november 2004
22:22:07


Could you
 
C

Chuck

You seem a good and friendly expert on this area. I am trying to
follow your advice in a similar problem: two XP pro's linked directly
together. One of the 2 PC's can ping the other but not the other way
around. When I switch the one that can see the other to safe mode,
entworking is fine. I ran PSLIST and looked at the differences but
couldn't find any obvious things. Then I tried to shut down all the
processes that were present on a normal login but not on a safe mode
login. At some stage, the computer shut down because I was closing
down too many processes.

Could you advise on what could cause the difference? I am trying to
figure it out for good after several trials that obviously weren't
successful. I always though it was my other machine causing the
problem because that is connected to internet and thus uses firewalls.
Hope you can help me.

thanX

Paul

Paul,

I'm happy to help, in many cases both you and I might learn from the experience.

But a couple notes to start.
1) Using PSList is generally more useful when all other analyses of a problem
have been tried, and no result reached.
2) When you post output from ipconfig and pslist, copied from Notepad, please
turn off Word Wrap (Format - Word Wrap) before selecting and copying the text.
This is particularly important for a detailed list like PSList. Please look at
the difference between the OPs posts and yours.
3) When you ask for help, its best if you start a new thread. Write an article
of your own, with a descriptive Subject, describing your problem, and starting
from the beginning. It's a lot easier for the many helpers here to see YOUR
problem if you start a thread, rather than asking for help in the thread where
someone else is being helped. And it's a lot easier to find any subsequent
replies, if they're in a unique thread, under YOUR name.

Anyway, from comparing the two process lists, I don't see anything recognisable.
What you might want to do, though, in addition to starting a new thread with
initial details of your problem, is to get Process Explorer (also free) (also
from SysInternals) at
<http://www.sysinternals.com/ntw2k/freeware/procexp.shtml>. PE will tell you
lots more about any processes which might be interesting.

And, as you've learned, researching a problem, by randomly shutting down
processes, is not a good idea. Here are a couple references where you might
look up processes (applications and services), before shutting them down:
Applications: <http://www.sysinfo.org/startuplist.php>
Applications: <http://www.liutilities.com/products/wintaskspro/processlibrary/>
Services: <http://www.blackviper.com/WinXP/servicecfg.htm>

BTW, Paul, please don't contribute to the spread and success of email address
mining viruses. Posting your email address openly will get you more unwanted
email, than wanted email. Learn to munge your email address properly, to keep
yourself a bit safer when posting to open forums. Protect yourself and the rest
of the internet - read this article.
http://www.mailmsg.com/SPAM_munging.htm

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
C

Chuck

pslist for safe modes......also i resolved my IP issue..........i had to
restart the router

PsList 1.26 - Process Information Lister
Copyright (C) 1999-2004 Mark Russinovich
Sysinternals - www.sysinternals.com

Process information for DELLFRONT1:

Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time
Idle 0 0 2 0 0 0:02:37.953 0:00:00.000
System 4 8 46 218 0 0:00:02.812 0:00:00.000
SMSS 516 11 3 21 164 0:00:00.171 0:01:17.578
CSRSS 564 13 11 247 1676 0:00:00.640 0:01:14.906
WINLOGON 588 13 20 254 3408 0:00:00.562 0:01:14.218
SERVICES 632 9 15 236 1812 0:00:00.296 0:01:12.203
LSASS 644 9 20 283 2100 0:00:00.203 0:01:11.937
SVCHOST 808 8 18 193 2836 0:00:00.093 0:01:09.781
SVCHOST 876 8 13 248 5024 0:00:00.187 0:01:09.046
SVCHOST 1088 8 35 497 10336 0:00:00.125 0:01:08.140
SVCHOST 1104 8 5 57 1040 0:00:00.046 0:01:07.984
SVCHOST 1248 8 3 102 2444 0:00:00.046 0:01:07.421
EXPLORER 1824 8 9 245 6108 0:00:02.250 0:00:53.250
CMD 1952 8 1 32 1876 0:00:00.062 0:00:41.062
pslist 2008 13 2 82 680 0:00:00.031 0:00:00.281



PsList 1.26 - Process Information Lister
Copyright (C) 1999-2004 Mark Russinovich
Sysinternals - www.sysinternals.com

Process information for COMPAQFRONT1:

Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time
Idle 0 0 1 0 0 0:12:31.812 0:00:00.000
System 4 8 43 229 0 0:00:02.562 0:00:00.000
smss 504 11 3 21 164 0:00:00.203 0:12:41.250
csrss 568 13 10 219 1752 0:00:01.500 0:12:36.484
winlogon 592 13 14 228 4060 0:00:01.468 0:12:34.218
services 636 9 15 236 1984 0:00:00.718 0:12:30.703
lsass 648 9 13 264 2012 0:00:00.750 0:12:30.515
svchost 804 8 16 187 2976 0:00:00.093 0:12:26.968
svchost 892 8 9 184 1684 0:00:00.125 0:12:26.078
svchost 1012 8 29 636 8920 0:00:00.687 0:12:25.546
svchost 1072 8 4 54 1156 0:00:00.062 0:12:25.390
svchost 1200 8 3 75 1188 0:00:00.078 0:12:24.578
explorer 1628 8 10 266 9536 0:00:04.796 0:12:09.734
cmd 2020 8 1 32 2032 0:00:00.062 0:00:34.281

OK, now we're at the point where you need to do some research.

Get Process Explorer (free) from
<http://www.sysinternals.com/ntw2k/freeware/procexp.shtml>. Provides way more
information than Task Manager.

Look at the PSList for CompaqFront1 (seems to be the computer with the problem).
Whitewash the entries on the Safe Mode process list. Use Process Explorer, on
CompaqFront1, to identify all entries not whitewashed. PE will show you (among
other things) which processes interact with TCP/IP. That, for my money, will be
a good place to start.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
G

Guest

good morning chuck,

One thing i failed to mention...the compaqfront1 has 2 operating systems on
it(xp home and pro) We always start in pro.... Would it be a good idea to get
rid of the home? if so how do you do that? ......... we do not use the other
OS for anything...nothing is installed...

Also how do you "whitewash"?
 
C

Chuck

good morning chuck,

One thing i failed to mention...the compaqfront1 has 2 operating systems on
it(xp home and pro) We always start in pro.... Would it be a good idea to get
rid of the home? if so how do you do that? ......... we do not use the other
OS for anything...nothing is installed...

Also how do you "whitewash"?

You want to research the processes in Normal Mode that aren't running in Safe
Mode. If a process is in Safe Mode, you aren't interested in it's entry in
Normal Mode. You "whitewash" (ignore) a process in the Normal Mode list, if
it's also present in the Safe Mode list.

As far as a computer with dual personality (operating systems), if properly
setup, the redundant operating systems shouldn't interfere with each other. How
are the two setup? They are using separate partitions, right?

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
G

Guest

yes they are on seperate partitions..


ok so i need to ignore everything on the list for safe mode for compaqfront1
right? is that where i use the "kill" in PE? I am sorry to sound like an
idiot...just trying to uderstand.... if not how do you ignore? and is this
process availiable in PE?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top