Re: Entire Network

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Tony Allen (tony.all_at_nbc.net)
Date: 09/23/04 

Date: Thu, 23 Sep 2004 15:37:25 -0700

Thanks Michael - Will do

I've set up many two and three home networks and have never had this issue.
The strange part is it worked here for weeks (since last OS install on the
Pro box and a new XP home computer) and a few days ago just poooooof!

"Michael Solomon (MS-MVP Windows Shell/User)" <user@#notme.com> wrote in
message news:uaHUKbboEHA.3988@tk2msftngp13.phx.gbl...
> First, Internet access is different and just because a firewall isn't
> blocking Internet access doesn't mean it's not blocking or in some fashion
> forcing the system to check items before allowing access to a file or
drive.
>
> Second, if it isn't the firewall, then often it is a case of the system
> polling the drives when you have a delay of the type you mention.
>
> These are the most common. However, this is not a network group nor am I
in
> any way a network guru. You might want to try your question on the
> windowsxp.network_web newsgroup.
>
> --
> Michael Solomon MS-MVP
> Windows Shell/User
> Backup is a PC User's Best Friend
> DTS-L.Org: http://www.dts-l.org/
>
> "Tony Allen" <tony.all@nbc.net> wrote in message
> news:OBo5bNboEHA.3564@tk2msftngp13.phx.gbl...
> > Thanks Michael - BTDT all.
> >
> > The network connection works just fine from both computers for internet
> > access.
> >
> > Folder sharing works just fine between both systems if I do the Add
> > Network
> > Places routine. It's the issue of the Entire Network | Microsoft Window
> > Network struggling (30 seconds) to find my 'HOME" network and then
getting
> > an error when I click on the "HOME" icon that's bugging me! Should not
> > one
> > system automatically detect folders on the other system that has been
> > marked
> > 'share', plus automatically recognizing the Shared Documents folder?
> >
> > Are there any services that may be not starting that could cause this?
> > I'm
> > just about ready to set them all to "automatic", reboot and see what
> > happens - unless you can advise other.
> >
> > Thanks for your assistance.
> >
> >
> > "Michael Solomon (MS-MVP Windows Shell/User)" <user@#notme.com> wrote in
> > message news:euAqhsaoEHA.1160@tk2msftngp13.phx.gbl...
> >> I can't tell whether or not you resolved the initial issue but there
are
> >> a
> >> few other possibilities with regard to what might be causing this.
> >> First,
> >> if either system is firewalled or both have firewalls, it's possible
you
> >> need to create a specific setting in the firewall to allow access. In
> > other
> >> words, if either system or both systems are firewalled, that could be
the
> >> issue.
> >>
> >> As to the initial issue, it's possible the problem is the default
setting
> > to
> >> assign IP addresses automatically. If that is the case, the following
> > might
> >> help:
> >> If you're running a DSL modem and have a LAN or high speed connection,
> >> try
> >> changing the properties of it.
> >>
> >> Go to start> connect to> show all connections>right click on Local Area
> >> connection>scroll down and click on Properties.
> >>
> >> Highlight "Internet protocol (TCP/IP)"
> >>
> >> Click on properties button>click on the "use the following IP address"
> > radio
> >> button.
> >>
> >> Add the following.
> >>
> >> IP address:192.168.0.1 (or any in the accepted range)
> >>
> >> Subnet Mask:255.255.255.0
> >>
> >> Some connections won't allow this, so if you can't get a connection,
> > remove
> >> it.
> >>
> >> If the above doesn't apply but you are on a network, go to Start\All
> >> Programs\Accessories and the Command Prompt. At the prompt type
> >> "ipconfig"
> >> without the quotes and press enter. Make note of the numbers.
> >>
> >> Go to Start\Connect To, select "Show all connections" and select Local
> > Area
> >> Connection. Right click and select properties. Select "Internet
Protocol
> >> (TCP/IP)" and click properties, select "Use the following IP address"
and
> >> input the appropriate numbers you found earlier. When you exit that
box,
> > the
> >> Subnet Mask numbers should input automatically.
> >>
> >> Reboot and see if that resolves the issue.
> >>
> >>
> >> --
> >> Michael Solomon MS-MVP
> >> Windows Shell/User
> >> Backup is a PC User's Best Friend
> >> DTS-L.Org: http://www.dts-l.org/
> >>
> >> "Tony Allen" <tony.all@nbc.net> wrote in message
> >> news:%23CzajlYoEHA.1664@tk2msftngp13.phx.gbl...
> >> > More info Tom -
> >> >
> >> > On both systems we can share folders and printers if I add them via
Add
> >> > Network Places and Add Printer (network) with the exception of the
> > Shared
> >> > Documents folder.
> >> >
> >> >
> >> > "Gordon" <gordonbp1@yahoo.invalid> wrote in message
> >> > news:%232NP6aYoEHA.2636@TK2MSFTNGP09.phx.gbl...
> >> >> "Tony Allen" <tony.all@nbc.net> wrote in message
> >> >> news:uiFq9XYoEHA.3988@tk2msftngp13.phx.gbl...
> >> >> > I have run (many times) the Network Setup Wizard on each of an XP
> >> >> > Pro
> >> > and
> >> >> an
> >> >> > XP Home computer. I just use the default name <MSHOME>.
> >> >> > However - when I then go to My Network Places | Entire Network |
> >> > Microsoft
> >> >> > Windows Network and click the system take about 30 seconds to find
> > the
> >> >> > MSHOME network. Then - if I click on MSHOME the systems search
for
> >> > about
> >> >> 45
> >> >> > seconds and then errors out with "Mshome not accessible. You might
> > not
> >> >> have
> >> >> > permission . . ."
> >> >> >
> >> >> >
> >> >> > can anyone offer any ideas?
> >> >> >
> >> >> >
> >> >>
> >> >> Have you ensured that each machine has an IDENTICALLY-NAMED User
> > account
> >> > set
> >> >> up, with IDENTICAL access rights and an IDENTICAL password?
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>

Quantcast