Iolo's System Mechanic 6 Disables all Windows Folder Sharing!

[Guest]

Well I am extremely frustrated with the result of running Iolo's System
Mechanic 6 demo. At one point I was actually quite impressed and was going to
purchase the software until I realized that it prevented all netbios access
to the computers where I ran it (2 out of 3 on my home lan). I can still
connect to the 3rd computer on which I did NOT run SM6. All computers are
loaded with XP pro. By the way, all TCP/IP networking is still completely OK.

I have tried uninstalling and reinstalling file & printer sharing. I re-ran
the XP network setup wizard. I have turned off the windows XP firewall (and
no other firewalls on any computer, except my router of course). I have
verified that all computers are named and share the same workgroup. I have
checked that folder shares have been created. I have tried connectiig using
Run \\ip_address which did not work. In the WINS tab of TCP/IP I have checked
that NETBIOS over TCP is on. I have tried undoing the SM6 changes. I have
sent iolo a help request 2 days ago but have not heard from them. I have
Googled the internet for information on this issue and did not come up with
much except this thread: http://www.techspot.com/vb/topic37527.html
I tried modifying the registry settings as per nedsram's suggestion but this
did not work for me.

If anyone has any ideas of how I can restore my network folder access I
would sure appreciate it. I would hate to be forced to reload XP due to
running the SM6 demo!

 

[Chuck]

Well I am extremely frustrated with the result of running Iolo's System
Mechanic 6 demo. At one point I was actually quite impressed and was going to
purchase the software until I realized that it prevented all netbios access
to the computers where I ran it (2 out of 3 on my home lan). I can still
connect to the 3rd computer on which I did NOT run SM6. All computers are
loaded with XP pro. By the way, all TCP/IP networking is still completely OK.

I have tried uninstalling and reinstalling file & printer sharing. I re-ran
the XP network setup wizard. I have turned off the windows XP firewall (and
no other firewalls on any computer, except my router of course). I have
verified that all computers are named and share the same workgroup. I have
checked that folder shares have been created. I have tried connectiig using
Run \\ip_address which did not work. In the WINS tab of TCP/IP I have checked
that NETBIOS over TCP is on. I have tried undoing the SM6 changes. I have
sent iolo a help request 2 days ago but have not heard from them. I have
Googled the internet for information on this issue and did not come up with
much except this thread: http://www.techspot.com/vb/topic37527.html
I tried modifying the registry settings as per nedsram's suggestion but this
did not work for me.

If anyone has any ideas of how I can restore my network folder access I
would sure appreciate it. I would hate to be forced to reload XP due to
running the SM6 demo!

One mention in DSLR Forums says that SM6 comes with Kaspersky's Personal
Anti-Virus and Firewall. KPF, if it works like MPF and NPF, will be a problem.
What other personal firewalls did you turn off? Remember many should be either
properly configured, or un installed.
<http://www.dslreports.com/forum/remark,15294179?hilite=iolo+system+mechanic>
http://www.dslreports.com/forum/remark,15294179?hilite=iolo+system+mechanic
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

If no help yet, provide "browstat status" and "ipconfig /all" from each
computer, so we can diagnose the problem. Read this article, and linked
articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

 

[Ron Lowe]

Well I am extremely frustrated with the result of running Iolo's System
Mechanic 6 demo. At one point I was actually quite impressed and was going
to
purchase the software until I realized that it prevented all netbios
access
to the computers where I ran it (2 out of 3 on my home lan). I can still
connect to the 3rd computer on which I did NOT run SM6. All computers are
loaded with XP pro. By the way, all TCP/IP networking is still completely
OK.

I have tried uninstalling and reinstalling file & printer sharing. I
re-ran
the XP network setup wizard. I have turned off the windows XP firewall
(and
no other firewalls on any computer, except my router of course). I have
verified that all computers are named and share the same workgroup. I have
checked that folder shares have been created. I have tried connectiig
using
Run \\ip_address which did not work. In the WINS tab of TCP/IP I have
checked
that NETBIOS over TCP is on. I have tried undoing the SM6 changes. I have
sent iolo a help request 2 days ago but have not heard from them. I have
Googled the internet for information on this issue and did not come up
with
much except this thread: http://www.techspot.com/vb/topic37527.html
I tried modifying the registry settings as per nedsram's suggestion but
this
did not work for me.

If anyone has any ideas of how I can restore my network folder access I
would sure appreciate it. I would hate to be forced to reload XP due to
running the SM6 demo!

Details, Details.
You'd need to do some tests, and provide the exact error messages you get at
each stage.

1) On each machine, from the command line, do the following:

ipconfig /all

Determine the IP address of each machine.
Determine the Node Type of each machine.

2) On each machine, from the command line, do the following:

ping 127.0.0.1
ping <machine's own IP address>
ping <other machine's IP address>
ping <other machine's name >

3) On each machine, from the command line, do the following:

net view
net view \\<other-machine-name>

4) What exact error do you get if you type \\<other-machine-name> at the
start - run box? You just said it didn't work. We need the exact and full
error.

What we're looking for is things like Error numbers ( eg, error5 or
error53 ), or specific messages about 'Access Denied' or 'Network Path Not
Found' or 'User has not been granted...' etc.

 

[TV-Engineer]

I have the same problem. Fortunately only installed on one computer. See
my answers to questions at the end.

Details, Details.
You'd need to do some tests, and provide the exact error messages you get
at each stage.

1) On each machine, from the command line, do the following:

ipconfig /all

results same on good and bad computer

Determine the IP address of each machine.
Determine the Node Type of each machine.

results the same on both computers

2) On each machine, from the command line, do the following:

ping 127.0.0.1

4 good replies

ping <machine's own IP address>

4 good replies

ping <other machine's IP address>

4 good replies

ping <other machine's name >

4 good replies

3) On each machine, from the command line, do the following:

net view

all computers in the workgroup listed

net view \\<other-machine-name>

from bad computer - shows shared folders of good computer
from good computer to bad - no response

4) What exact error do you get if you type \\<other-machine-name> at the
start - run box? You just said it didn't work. We need the exact and full
error.

good computer shows shares on another good computer,
on bad computer - 'windows cannot find 'computer name'. Make sure you typed
the name correctly, and then try again. To search for a file, click the
start button, and then click search.

opening workgroup on all computers shows all computers in the workgroup.

on the bad computer, clicking on any computer results in all shares being
shown

on a good computer, clicking on the bad computer results in the following
\\bad computer is not accessable. you might not have permission to use this
network resource. Contact the administrator of the server to find out if
you have access permissions.. The specified network name is no longer
available.

Eric

 

[Guest]

Re:

Details, Details.
You'd need to do some tests, and provide the exact error messages you get at
each stage.

1) On each machine, from the command line, do the following:

ipconfig /all

Determine the IP address of each machine.
Determine the Node Type of each machine.

2) On each machine, from the command line, do the following:

ping 127.0.0.1
ping <machine's own IP address>
ping <other machine's IP address>
ping <other machine's name >

3) On each machine, from the command line, do the following:

net view
net view \\<other-machine-name>

4) What exact error do you get if you type \\<other-machine-name> at the
start - run box? You just said it didn't work. We need the exact and full
error.

Well I did some testing and have some results.

Just to summarize, I have 3 computers:

(1) DELL8250 192.168.15.100 (ran system mechanic 6 demo)
(2) DELL4600 192.168.15.101 (ran system mechanic 6 demo)
(3) XPSGEN2 192.168.15.102 (did NOT run system mechanic 6 demo)

Here are the results:

1) On each machine, from the command line, do the following:

ipconfig /all

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

C:\Documents and Settings\Peter>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DELL8250
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.mi.comcast.net.

Ethernet adapter Home LAN:

Connection-specific DNS Suffix . : hsd1.mi.comcast.net.
Description . . . . . . . . . . . : Intel(R) PRO/100 M Network
Connection
Physical Address. . . . . . . . . : 00-07-E9-C9-CF-81
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.15.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.15.1
DHCP Server . . . . . . . . . . . : 192.168.15.1
DNS Servers . . . . . . . . . . . : 68.87.77.130
68.87.72.130
Lease Obtained. . . . . . . . . . : Friday, January 27, 2006
10:22:46 PM

Lease Expires . . . . . . . . . . : Saturday, January 28, 2006
10:22:46 PM

DELL4600:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Dell4600
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.mi.comcast.net.

Ethernet adapter Wireless Network Connection 3:

Connection-specific DNS Suffix . : hsd1.mi.comcast.net.
Description . . . . . . . . . . . : WPN311 RangeMax(TM) Wireless PCI
Adapter
Physical Address. . . . . . . . . : 00-0F-B5-88-D7-8C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.15.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.15.1
DHCP Server . . . . . . . . . . . : 192.168.15.1
DNS Servers . . . . . . . . . . . : 68.87.77.130
68.87.72.130
Lease Obtained. . . . . . . . . . : Friday, January 27, 2006
11:35:31 PM

Lease Expires . . . . . . . . . . : Saturday, January 28, 2006
11:35:31 PM

XPSGEN2:
Windows IP Configuration

Host Name . . . . . . . . . . . . : XPSGen2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.mi.comcast.net.

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom 570x Gigabit Integrated
Con
troller
Physical Address. . . . . . . . . : 00-11-43-78-3E-F9

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . : hsd1.mi.comcast.net.
Description . . . . . . . . . . . : NETGEAR RangeMax(TM) Wireless PC
Card WPN511
Physical Address. . . . . . . . . : 00-0F-B5-AA-28-76
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.15.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.15.1
DHCP Server . . . . . . . . . . . : 192.168.15.1
DNS Servers . . . . . . . . . . . : 68.87.77.130
68.87.72.130
Lease Obtained. . . . . . . . . . : Saturday, January 28, 2006
12:03:14AM
Lease Expires . . . . . . . . . . : Sunday, January 29, 2006
12:03:14 AM

----------
Browstat results:

DELL8250:
C:\Documents and Settings\Peter>browstat status


Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{E246B662-B68F-48E7-87
C2-4A83ED9463EB}
Browsing is active on domain.
Master browser name is: DELL8250
Master browser is running build 2600
1 backup servers retrieved from master DELL8250
\\DELL8250
Unable to retrieve server list from DELL8250: 121

DELL4600:
C:\Program Files\Support Tools>browstat status


Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{DC9FB018-19C5-4530-88
AB-389CE92A9F86}
Browsing is active on domain.
Master browser name is: DELL8250
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
Unable to determine server information for browser master: 1231
1 backup servers retrieved from master DELL8250
\\DELL8250
Unable to retrieve server list from DELL8250: 1231

XPSGEN2:
Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{B27FA962-9BFA-40E4-B9
EC-5EE57F223DF5}
Browsing is active on domain.
Master browser name is: DELL8250
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
Unable to determine server information for browser master: 53
1 backup servers retrieved from master DELL8250
\\DELL8250
Unable to retrieve server list from DELL8250: 121
---------------------------------------------------------------------------

2) On each machine, from the command line, do the following:

ping 127.0.0.1
ping <machine's own IP address>
ping <other machine's IP address>
ping <other machine's name >

DELL8250:
ping 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=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64

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

ping <machine's own IP address>

Pinging 192.168.15.100 with 32 bytes of data:

Reply from 192.168.15.100: bytes=32 time<1ms TTL=64
Reply from 192.168.15.100: bytes=32 time<1ms TTL=64
Reply from 192.168.15.100: bytes=32 time<1ms TTL=64
Reply from 192.168.15.100: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.15.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

ping <other machine's IP address>
ping <other machine's name >

Pinging 192.168.15.101 with 32 bytes of data:

Reply from 192.168.15.101: bytes=32 time=3ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.15.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 1ms

Pinging dell4600 [192.168.15.101] with 32 bytes of data:

Reply from 192.168.15.101: bytes=32 time=1ms TTL=64
Reply from 192.168.15.101: bytes=32 time=2ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.15.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

Pinging 192.168.15.102 with 32 bytes of data:

Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.15.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

Pinging xpsgen2 [192.168.15.102] with 32 bytes of data:

Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.15.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

DELL4600:

ping 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=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64

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

ping <machine's own IP address>

Pinging 192.168.15.101 with 32 bytes of data:

Reply from 192.168.15.101: bytes=32 time<1ms TTL=64
Reply from 192.168.15.101: bytes=32 time<1ms TTL=64
Reply from 192.168.15.101: bytes=32 time<1ms TTL=64
Reply from 192.168.15.101: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.15.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

ping <other machine's IP address>

Pinging 192.168.15.100 with 32 bytes of data:

Reply from 192.168.15.100: bytes=32 time=2ms TTL=64
Reply from 192.168.15.100: bytes=32 time=1ms TTL=64
Reply from 192.168.15.100: bytes=32 time=1ms TTL=64
Reply from 192.168.15.100: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.15.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

ping <other machine's name >

Pinging dell8250 [192.168.15.100] with 32 bytes of data:

Reply from 192.168.15.100: bytes=32 time=1ms TTL=64
Reply from 192.168.15.100: bytes=32 time=1ms TTL=64
Reply from 192.168.15.100: bytes=32 time=1ms TTL=64
Reply from 192.168.15.100: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.15.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

Pinging 192.168.15.102 with 32 bytes of data:

Reply from 192.168.15.102: bytes=32 time=4ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.15.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 1ms

Pinging xpsgen2 [192.168.15.102] with 32 bytes of data:

Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128
Reply from 192.168.15.102: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.15.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

XPSGEN2:

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

ping <machine's own IP address>

Pinging 192.168.15.102 with 32 bytes of data:

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

Ping statistics for 192.168.15.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

ping <other machine's IP address>
ping <other machine's name >

Pinging 192.168.15.101 with 32 bytes of data:

Reply from 192.168.15.101: bytes=32 time=7ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.15.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 7ms, Average = 2ms

Pinging dell4600 [192.168.15.101] with 32 bytes of data:

Reply from 192.168.15.101: bytes=32 time=1ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64
Reply from 192.168.15.101: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.15.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

Pinging 192.168.15.100 with 32 bytes of data:

Reply from 192.168.15.100: bytes=32 time=3ms TTL=64
Reply from 192.168.15.100: bytes=32 time=2ms TTL=64
Reply from 192.168.15.100: bytes=32 time=1ms TTL=64
Reply from 192.168.15.100: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.15.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 1ms

Pinging dell8250 [192.168.15.100] with 32 bytes of data:

Reply from 192.168.15.100: bytes=32 time=1ms TTL=64
Reply from 192.168.15.100: bytes=32 time=1ms TTL=64
Reply from 192.168.15.100: bytes=32 time=1ms TTL=64
Reply from 192.168.15.100: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.15.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
-----------------------------------------------

3) On each machine, from the command line, do the following:

net view
net view \\<other-machine-name>
DELL8250:
net view

Server Name Remark

-------------------------------------------------
\\DELL4600 Kitchen Computer
\\DELL8250 Den Computer
\\XPSGEN2 Laptop
The command completed successfully.

net view \\<other-machine-name>

C:\Documents and Settings\Peter>net view \\dell4600
System error 64 has occurred.

The specified network name is no longer available.

C:\Documents and Settings\Peter>net view xpsgen2
Shared resources at xpsgen2

Laptop

Share name Type Used as Comment

-----------------------------------------------------
C Disk
Kids Disk
Peter Disk
Printer Print Intuit Internal Printer
SharedDocs Disk
The command completed successfully.

DELL4600:

net view

C:\Documents and Settings\Peter>net view
System error 121 has occurred.

The semaphore timeout period has expired.

net view \\<other-machine-name>

C:\Documents and Settings\Peter>net view \\dell8250
System error 64 has occurred.

The specified network name is no longer available.

C:\Documents and Settings\Peter>net view \\xpsgen2
Shared resources at \\xpsgen2

Laptop

Share name Type Used as Comment

----------------------------------------------------------
C Disk
Kids Disk
Peter Disk
Printer Print Intuit Internal Printer
SharedDocs Disk
The command completed successfully.

XPSGEN2:

net view

C:\Documents and Settings\Peter>net view
System error 64 has occurred.

The specified network name is no longer available.

net view \\<other-machine-name>

C:\Documents and Settings\Peter>net view dell8250
System error 64 has occurred.

The specified network name is no longer available.


C:\Documents and Settings\Peter>net view dell4600
System error 64 has occurred.

The specified network name is no longer available.

4) What exact error do you get if you type \\<other-machine-name> at the
start - run box? You just said it didn't work. We need the exact and full
error.

From all machines when I try connecting to one of the "bad" machines using
either the Run "\\computer" format or the Run "\\IP_address" format, I get
the same error in a dialog box:

"The specified network name is no longer available"

 

[Guest]

One mention in DSLR Forums says that SM6 comes with Kaspersky's Personal
Anti-Virus and Firewall. KPF, if it works like MPF and NPF, will be a problem.
What other personal firewalls did you turn off? Remember many should be either
properly configured, or un installed.

Although I loaded System Mechanic Pro 6 I did *not* load the firewall or
antivirus option. I have no personal firewalls loaded on any of the 3
computers except of course the built-in windows firewall which I have
validated is off on all 3 machines.

Read this article, and linked

articles, and follow instructions precisely:

http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

This is a great resource to aid in debugging. I had already done most of the
checks listed however there are a few new ones that I was unaware of, however
I found no problems other then what I have already identified. I was
wondering if I should go ahead and try running "WinSock XP Fix" and also
reset TCP/IP in Windows XP? Could this cause additional problems or will
returning to a previous restore point cleany back off the changes if I run
into problems?

 

[Chuck]

Although I loaded System Mechanic Pro 6 I did *not* load the firewall or
antivirus option. I have no personal firewalls loaded on any of the 3
computers except of course the built-in windows firewall which I have
validated is off on all 3 machines.

Read this article, and linked


This is a great resource to aid in debugging. I had already done most of the
checks listed however there are a few new ones that I was unaware of, however
I found no problems other then what I have already identified. I was
wondering if I should go ahead and try running "WinSock XP Fix" and also
reset TCP/IP in Windows XP? Could this cause additional problems or will
returning to a previous restore point cleany back off the changes if I run
into problems?

My personal opinion is that, if your network isn't working, running "WinSock XP
Fix", and its peers, won't make it any worse. But you should do a System
Restore before, and after, just in case I'm wrong. And please try more than
just "WinSock XP Fix" - there are several peer solutions to that. Read the LSP
corruption article:
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

 

[TV-Engineer]

Running winsockxpfix.exe restores normal operation on my affected computer.

Thank you.

Eric

 

[Chuck]

On Sun, 29 Jan 2006 22:48:08 -0500, "TV-Engineer"

Thanks for the feedback, Eric.

 

[BrianW]

Well I am extremely frustrated with the result of running Iolo's System
Mechanic 6 demo. At one point I was actually quite impressed and was going
to
purchase the software until I realized that it prevented all netbios
access
to the computers where I ran it (2 out of 3 on my home lan). I can still
connect to the 3rd computer on which I did NOT run SM6. All computers are
loaded with XP pro. By the way, all TCP/IP networking is still completely
OK.

I have tried uninstalling and reinstalling file & printer sharing. I
re-ran
the XP network setup wizard. I have turned off the windows XP firewall
(and
no other firewalls on any computer, except my router of course). I have
verified that all computers are named and share the same workgroup. I have
checked that folder shares have been created. I have tried connectiig
using
Run \\ip_address which did not work. In the WINS tab of TCP/IP I have
checked
that NETBIOS over TCP is on. I have tried undoing the SM6 changes. I have
sent iolo a help request 2 days ago but have not heard from them. I have
Googled the internet for information on this issue and did not come up
with
much except this thread: http://www.techspot.com/vb/topic37527.html
I tried modifying the registry settings as per nedsram's suggestion but
this
did not work for me.

If anyone has any ideas of how I can restore my network folder access I
would sure appreciate it. I would hate to be forced to reload XP due to
running the SM6 demo!

You are not alone. This is a dreadful piece of software. The people who
wrote it like to play god, and make arbitrary and unspecified changes to
system settings that were just fine. It took me days to get my network drive
visible to other PCs again. They seem to think that allowing other PCs on
your Intranet to acess your shared drive is a "security risk" which must be
fixed at all costs. Tough luck if it completely screws up your PC in the
process. You might like to have a look at this thread:

http://www.techspot.com/vb/topic37527.html

What's even worse than the software itself is that it's "highly recommended"
by ZoneLabs. If they hadn't offered it to me at a discounted price I might
never have heard of it, let alone bought the thing!

Brian

 

[Chuck]

You are not alone. This is a dreadful piece of software. The people who
wrote it like to play god, and make arbitrary and unspecified changes to
system settings that were just fine. It took me days to get my network drive
visible to other PCs again. They seem to think that allowing other PCs on
your Intranet to acess your shared drive is a "security risk" which must be
fixed at all costs. Tough luck if it completely screws up your PC in the
process. You might like to have a look at this thread:

http://www.techspot.com/vb/topic37527.html

What's even worse than the software itself is that it's "highly recommended"
by ZoneLabs. If they hadn't offered it to me at a discounted price I might
never have heard of it, let alone bought the thing!

Brian

Brian,

You make valid points. No matter what software you run on your computer, you
had better know what it does, and that what it does agree with your needs. From
registry "cleaner" programs to system "optimiser" programs, there's a hella lot
of snake oil out there.

I research software very carefully. Read my article, if you like.
<http://nitecruzr.blogspot.com/2005/12/download-software-selectively.html>
http://nitecruzr.blogspot.com/2005/12/download-software-selectively.html

 

[BrianW]

I research software very carefully. Read my article, if you like.

<http://nitecruzr.blogspot.com/2005/12/download-software-selectively.html>
http://nitecruzr.blogspot.com/2005/12/download-software-selectively.html

Once bitten twice shy. My mistake was to assume that they would first tell
you what the problems were, then allow you to select which ones you wanted
them to fix. Instead they just jumped in and screwed things up without as
much as a "please can I".

As for suggestions that you could "undo" the changes, that wasn't possible
in the version I used, although I believe that in response to customer (to
be polite) "feedback", they did later add this. However even the option had
been there, the UI was so dreadful that it would have been hard to track
down this option.

Thanks for the links. I'm not usually caught out like this, and in future I
too will research products carefully before using them!

Brian

 

[Guest]

Chuck:

Running Winsock XP Fix worked for me as well!! THANK-YOU for steering me in
the right direction to resolve this. I must have spent over 10 hours trying
to solve this. As for Iolo I am VERY displeased with their product and their
support - I have not even received a response after 5 days.

 

[Guest]

If you want a laugh, check out the Amazon.com page for System Mechanic 6. The
price has been dropped to $20 and check out over 30 very negative customer
reviews!

 

[TV-Engineer]

Just received a response from IOLO - telling me to immediately uninstall
System Mechanic 6 and download and install the current version on their
site. Also said a new version will be available within 72 hours.

Eric

 

[Chuck]

Chuck:

Running Winsock XP Fix worked for me as well!! THANK-YOU for steering me in
the right direction to resolve this. I must have spent over 10 hours trying
to solve this. As for Iolo I am VERY displeased with their product and their
support - I have not even received a response after 5 days.

That's great news - thanks for the update!

Now look at the other half of your hijacked thread - the hijacker is claiming
that he was told by Iolo to uninstall the current version and install a new
IMPROVED version. Hmm? Do you trust them now?

 

[Chuck]

Just received a response from IOLO - telling me to immediately uninstall
System Mechanic 6 and download and install the current version on their
site. Also said a new version will be available within 72 hours.

Eric

HaHa. Do you trust them?