Re: Can't Set-up Home Network



On Wed, 31 Aug 2005 21:23:02 -0700, "jwolfdog"
<jwolfdog@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>"Allen" wrote:
>
>>
>>
>> "Chuck" wrote:
>>
>> > On Wed, 24 Aug 2005 20:33:16 -0700, "jwolfdog"
>> > <jwolfdog@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>> >
>> > >I can't set-up a home network successfully after adding a new computer
>> > >running XP sp2. After running the Home Networking Wizard on my new XP machine
>> > >adn teh tow odler Windows ME computers, I get an error message on the XP
>> > >machine that states: "Mshome is not accessible. You might not have permission
>> > >to use this network resource. Contact your system administrator."
>> > >
>> > >I have a new Dell running XP, an older Dell running Windows ME, and an older
>> > >Dell laptop running ME as well. The two desktop machines are connected to a
>> > >Linksys router via Ethernet cables, and the laptop connects to the router
>> > >wirelessly. They can all get out to the Internet, and the two ME machines can
>> > >recognize each other on the home network, but not they cannot "see" the XP
>> > >machine through Network Neighborhood. And the XP machine cannot "see" either
>> > >of the two ME machines through Network Neighborhood. So, there is no ability
>> > >to file share between the XP machine and the other two. And neither ME
>> > >machines can print to the printer connected to the XP machine via its USB
>> > >port.
>> > >
>> > >Ironically, when I first unboxed the XP machine I was able to connect it to
>> > >the network and access the older Dell desktop machine and successfully
>> > >transfer the files from the old machine to our new one. But then I thought I
>> > >had to run the Home Networking wizard on the XP machine, run the its wizard
>> > >on the two ME machines. After that, I had the problem.
>> > >
>> > >I've used the networking troubleshooter, but it hasn't given me the
>> > >directions that solve the problem.
>> > >
>> > >I hope someone can solve this for me.
>> > >
>> > >Thanks.
>> > >
>> > >*email_address_deleted*
>> >
>> > Combining Windows 9x (95, 98, ME) and Windows NT (NT, 2000, XP) computers in a
>> > workgroup will always be problematic.
>> > <http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
>> >
>> > Also, check for misconfigured / overlooked firewalls, and for the registry
>> > setting restrictanonymous on the XP computer.
>> > Misconfigured / overlooked firewalls:
>> > <http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
>> > Registry setting restrictanonymous:
>> > <http://nitecruzr.blogspot.com/2005/07/restrictanonymous-and-your-server.html>
>> >
>> > If no help yet, provide "browstat status" and "ipconfig /all" from each
>> > computer, and we'll diagnose the problem. Read this article, and linked
>> > articles, and follow instructions precisely:
>> > <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
>> >
>> > Please let us know if any of these suggestions are of any help. What you learn
>> > may help others in the future, and that's the purpose of these forums.
>> >
>> > BTW, 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://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#Munging>

>"Chuck":
>
>Thank you for your reply. Unfortunately, when I clicked on your links I got
>an Page not found error 404. I did read over your reply as best I could.
>
>There were two things I wanted to follow up with.
>
>1.) The thing I still am stuck on is that the networking worked BEFORE I
>used the XP Networking Wizard. Despite what you wrote about that networking
>between 98-based machines and NT-based machines being problematic, I could
>connect to the other computers on the network. Isn't there a way I can simply
>"undo" that process and return to the out-of-the-box state before I ran the
>XP networking wizard?
>
>2.) I am a relatively inexperienced at setting up Windows networks. So,
>unfortunately much of what you referred to "registries", etc. seem quite
>complex. Isn't there a simpler way to get at the fact the I get this message
>back that says "Mshome not accessible"? Why isn't the workgroup Mshome
>accessible?
>
>Lastly, while I think Microsoft should be able to make a home network
>function that uses ME and XP, would it be the simplest solution (although not
>the cheapest) to put XP on the other computers? Would that solve the problem?
>Or is the problem I am having something fouled-up on this new Dell running XP?
>
>I'd appreciate yours, or anyone's 2nd try with me. Also, it was interesting
>to see "Allen's" post which closely echoed mine. Did he get it solved?
>
>Thanks for the help,
>
>jwolfdog

I assure you, the blogspot website exists. Do you see the "<" and ">" at either
end of the URLs? Is the complete URL inside those characters making its way
into the address field in your browser? Are you removing the "<" and ">" before
hitting enter (you should)?

You really need to read those articles. There's a lot of information there, in
hypertext, which will be really hard to extract here. I'll summarise as best I
can.

The error "MSHome not accessible" can have many causes, from a simple cable
problem (no connectivity), to a firewall or permission problem. With a Windows
9x (95, 98, ME) and NT (NT, 2000, XP) combination, one of the most likely causes
is the browser. The Windows 9x and NT browsers don't co exist well. They may
work for a while, as yours did, but don't work now.

Replacing the Windows ME computer with another Windows XP computer would be a
good workaround for the browser problem, but you may still need to tune your
LAN. And that may mean reading some of my articles.

And I sympathise with your not understanding the registry, but you're going to
have to try. I'm giving you the benefit of my experience, you're going to have
to try and follow along. Obviously, the first thing that you have to do is to
read the articles that I provided. And, when the registry is involved in a
problem, you're going to have to access, and edit, the registry.

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.



Relevant Pages

  • Re: BAD ATTITUDE
    ... Networking and Security is covered fully in Help by some ... These are supplemented by Knowledge Base Articles and web information, ... > tech articles on How Windows works and how to work with it. ...
    (microsoft.public.windowsxp.general)
  • Re: Recent Files list - Is there a simple way?
    ... Find great Windows Forms articles in Windows Forms Tips and Tricks ... I am thinking of adding an entry in registry whenever the ... >> Since this functionality is very common, I am wondering is there a built ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: Recent Files list - Is there a simple way?
    ... > Find great Windows Forms articles in Windows Forms Tips and Tricks ... I am thinking of adding an entry in registry whenever ... >>> Since this functionality is very common, I am wondering is there a built ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: "DNS Client" service: What are the correct parameters?
    ... between Windows 2000 and XP. ... > these parameters exist under the mentioned key in my registry but then ... > NegativeCacheTime, NetFailureCacheTime, and NegativeSOACacheTime. ... > Windows XP versus the TTL values mentioned above in the other articles. ...
    (microsoft.public.windows.server.dns)
  • Re: controls init from registry
    ... Generally you can load and save at any time. ... > registry when you need to read a value. ... > Find great Windows Forms articles in Windows Forms Tips and Tricks ...
    (microsoft.public.dotnet.framework.windowsforms.controls)