lost workstation

[chale]

Windows 2003 Server and Windows XP Pro with Svc pack #1
workstation.

This workstation began running extremely slow. In an
effort to troubleshoot this problem, uning msconfig, I
stopped many of the running services and programs. I
have since started them all back up, however, the machine
will not hit the network now. What do I need to do to
get back on the network? Thanks in advance.

Craig,

 

[Chuck]

Windows 2003 Server and Windows XP Pro with Svc pack #1
workstation.

This workstation began running extremely slow. In an
effort to troubleshoot this problem, uning msconfig, I
stopped many of the running services and programs. I
have since started them all back up, however, the machine
will not hit the network now. What do I need to do to
get back on the network? Thanks in advance.

Craig,

Craig,

You have just provided a textbook example why MSConfig is not a good diagnostic
/ optimisation tool. Stopping services, without recording what you stopped, is
not a good idea.

BlackViper provides a good list of what services are necessary, and what
services are recommended.
<http://www.blackviper.com/WIN2K/servicecfg.htm>
<http://www.blackviper.com/WinXP/servicecfg.htm>

Beyond that, we can probably help you get your network working again, if you'll
provide exact symptoms of "the machine will not hit the network now". Here are
some simple tests that might get us started too.

Make sure the browser service is running. Control Panel - Administrative Tools
- Services. Verify that the Computer Browser service is started.

Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
Identify operating system (by name and version) with each ipconfig listing.

From each computer, test connectivity:
1) Ping itself by name.
2) Ping itself by ip address.
3) Ping the other by name.
4) Ping the other by ip address.
5) Ping 127.0.0.1.
6) Ping the router.
Report success / exact error displayed in each test (12 tests total).

From each computer, test shares visibility (use actual name / address of each
computer as appropriate):
Start - Run then:
1) \\ThisComputerByName
2) \\ThisComputerByIPAddress
3) \\OtherComputerByName
4) \\OtherComputerByIPAddress
Report visibility of shares / exact error displayed in each test (8 tests
total).

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

 

[Craig Hale]

-----Original Message-----


Craig,

You have just provided a textbook example why MSConfig is not a good diagnostic
/ optimisation tool. Stopping services, without recording what you stopped, is
not a good idea.

BlackViper provides a good list of what services are necessary, and what
services are recommended.
<http://www.blackviper.com/WIN2K/servicecfg.htm>
<http://www.blackviper.com/WinXP/servicecfg.htm>

Beyond that, we can probably help you get your network working again, if you'll
provide exact symptoms of "the machine will not hit the network now". Here are
some simple tests that might get us started too.

Make sure the browser service is running. Control Panel - Administrative Tools
- Services. Verify that the Computer Browser service is started.

Please provide ipconfig information for each computer.
Start - Run - "cmd". Type "ipconfig /all
c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, copy and paste into your next post.
Identify operating system (by name and version) with each ipconfig listing.

From each computer, test connectivity:
1) Ping itself by name.
2) Ping itself by ip address.
3) Ping the other by name.
4) Ping the other by ip address.
5) Ping 127.0.0.1.
6) Ping the router.
Report success / exact error displayed in each test (12 tests total).

From each computer, test shares visibility (use actual name / address of each
computer as appropriate):
Start - Run then:
1) \\ThisComputerByName
2) \\ThisComputerByIPAddress
3) \\OtherComputerByName
4) \\OtherComputerByIPAddress
Report visibility of shares / exact error displayed in each test (8 tests
total).

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

Thank you Chuck. I have been out of town and just now
able to work on this some. I will do as you suggest and
be back with you. I do appreciate these tips.

Craig,