Home Network unavailable

  • Thread starter Thread starter Michael M
  • Start date Start date
M

Michael M

After installing MSAS I can no longer access computers on
my home network. I can get to the internet just fine.
If I try to access a computer from the Run command with a
statement such as \\Machine1, I get an error stating that
\\Machine1 is unavailable or I might not have
permissions. I get the same error if I go to Machine1
and try to access my laptop computer. If I try to browse
Network Neighborhood, I only see my computer, not
Machine1. I have been copying files and printing to this
machine for 2 years now. So I do not know why it
suddenly does not work. Right now I am back to the old
sneaker-net which really sucks. Any idea what MSAS may
have disabled? If I exit MSAS, I still cannot access the
other computer on the home network.
 
After installing MSAS I can no longer access computers on
my home network. I can get to the internet just fine.
If I try to access a computer from the Run command with a
statement such as \\Machine1, I get an error stating that
\\Machine1 is unavailable or I might not have
permissions. I get the same error if I go to Machine1
and try to access my laptop computer. If I try to browse
Network Neighborhood, I only see my computer, not
Machine1. I have been copying files and printing to this
machine for 2 years now. So I do not know why it
suddenly does not work. Right now I am back to the old
sneaker-net which really sucks. Any idea what MSAS may
have disabled? If I exit MSAS, I still cannot access the
other computer on the home network.
Click to expand...

Please take a look here http://support.microsoft.com/kb/892350
 
Thanks, I saw a reference to this knowledge base article
when reading a similar post. But I do not receive any of
the 3 error message stated under symptoms.

Mike
 
Thanks, I saw a reference to this knowledge base article
when reading a similar post. But I do not receive any of
the 3 error message stated under symptoms.

Mike
Click to expand...

OK, so if the MSAS is running, you cannot access the network, but when you
shut it down are you able to access the network again?
 
I am having a similar problem, but I'm sure it is NOT
directly related to having INSTALLED the program. I
installed and ran it last night. It worked great and
identifying and removing 4 threats, including Marketscore
and Comet. The problem I now have is that I have to
manually set all the values in TCP/IP to try to connect to
my home network, and though the connection settings tell
my I'm connected, the machine does not show up in the DHCP
table in my gateway/router program. My other programs run,
but I cannot connect at all to the internet on that
machine. This also happened recently when I used Norton
Internet Security 2005 (antispyware version) to remove the
spyware, and I eventually ended up having to revert to
using a full-system backup to restore my internet
functionality.

The closest solution that I have found is one on the
Symantec Security web site that deals with removal of
Trojans and worms, and how the process can leave your
system unable to open programs due to changes made to the
registry. (See
http://service1.symantec.com/support/nav.nsf/pfdocs/2000051
114441106). Fortunately (I think) I created a resore
point in System Restore just before I let the Spyware
Program remove the spyware. (I haven't had much luck with
the System Restore in the past; it has always told me it
can't restore to the point I want to restore to). I just
don't want to go BACK if I don't have to. I'd like to get
this issue resolved, once and for all (and quickly create
a new backup; the spyware was included in my other backup
image).

I'm not sure at this point, but it looks like I either
have one or more registry entries that are trying to find
the spyware, OR one of the registry entries that was
deleted has a key to connecting to the internet. All of
the other machines on my home network are working fine,
including 2 that are connected by hardwire, and 2 that are
running on wireless to my gateway/router.

If I set my TCP/IP settings to all automatic, the status
of the connection shows that I have minimal or no
connectivity, and the IP address is consistently set to
169.254.xxx.xxx (the last numbers vary depending on when I
try this) with a subnet mask always of 255.255.0.0

Anyone have any ideas?? I've been trying to fix this issue
for about a month.

Sincerely

Al
Washington state
 
Mikolaj, you are my savior today! Many thanks!! After my
last post, I did go to the web page you recommended, and
tried it. It worked great, at least for my wireless
connection.
After doing this, I was able to re-enable my Linksys
wireless connection, and can now connect to the internet
again. However when I disable my wireless connection, and
enable my hardwire 10/100 network connection, I am still
unable to obtain an IP address. (It defaults to
169.254.xxx.xxx (x's change with each attempt) and a
subnet mask of 255.255.0.0.). This is what both adapters
were doing before I reset the WinSock catalog. If I
disable the 10/100, and enable the wireless adapter, it is
able to obtain an IP address and I am once again able to
connect to the internet. Both adapters are set for
automatic configurations of TCP/IP.

Any ideas on how I might repair the 10/100 connection?

And Mike, you may want to give this a try. The page is not
JUST for the 3 error messages listed. It is also for the 3
items listed below the error messages.

Thanks again, Mikolaj!

Sincerely,

Al
Washington State
 
Mikolaj, you are my savior today! Many thanks!! After my
last post, I did go to the web page you recommended, and
tried it. It worked great, at least for my wireless
connection.
After doing this, I was able to re-enable my Linksys
wireless connection, and can now connect to the internet
again. However when I disable my wireless connection, and
enable my hardwire 10/100 network connection, I am still
unable to obtain an IP address. (It defaults to
169.254.xxx.xxx (x's change with each attempt) and a
subnet mask of 255.255.0.0.). This is what both adapters
were doing before I reset the WinSock catalog. If I
disable the 10/100, and enable the wireless adapter, it is
able to obtain an IP address and I am once again able to
connect to the internet. Both adapters are set for
automatic configurations of TCP/IP.

Any ideas on how I might repair the 10/100 connection?

And Mike, you may want to give this a try. The page is not
JUST for the 3 error messages listed. It is also for the 3
items listed below the error messages.

Thanks again, Mikolaj!

Sincerely,

Al
Washington State
Click to expand...

Hi,

I'm glad that could be helpful :-)

About this hardwire connection problem - this kind of IP address (i.e.
169.254.x.x/16) is assigned automatically by Windows when it is set to
acquire IP settings automatically from DHCP server, but such server is
unavailable (this mechanism is called APIPA). So the problem may be not at
system level, but on the wire/network level - for example the DHCP has been
removed from your network, the hardwire has been damaged and so on.. So
please check also this "hardware" possibility.
 
Mikolaj brought next idea :
Hi,

I'm glad that could be helpful :-)

About this hardwire connection problem - this kind of IP address (i.e.
169.254.x.x/16) is assigned automatically by Windows when it is set to
acquire IP settings automatically from DHCP server, but such server is
unavailable (this mechanism is called APIPA). So the problem may be not at
system level, but on the wire/network level - for example the DHCP has been
removed from your network, the hardwire has been damaged and so on.. So
please check also this "hardware" possibility.
Click to expand...

Hi Al and Mikolaj.

This kb and update is also important for WiFi networks.

http://support.microsoft.com/?id=893357

I have never seen it on Windowsupdate ?
 
Back
Top