From: "Geo" 

It almost sounds like broadcast traffic is being blocked on one or more of
the machines.

Geo.

"Rich Gauszka"  wrote in message
news:42d5c288$1{at}w3.nls.net...
> Hp Printer worked after I put an entry into the hosts file for it. I guess
> MS really 'secured' my XP Home network with the update
>
>
> "Rich Gauszka"  wrote in message
> news:42d5c086$1{at}w3.nls.net...
> > The share works fine with another XP Pro computer
> >
> > The My Computer  Computer Name   is xyzaspire
> >
> > I put an entry in the hosts file on the XP Home machine so I can
continue
> > to access the share by computer name. Doing a browse in 'Map the Network
> > drive' with the XP Home pc shows nothing under the workgroup. This
worked
> > prior to the Windows Update this morning. The XP Home pc is the only one
> > that's given any problems and it's the only XP Home pc that I have to
test
> > with as both the laptop and media pc are XP Pro.
> >
> > I was going to say that it wasn't a biggie but I just discovered that my
> > wireless all-in-one HP psc 2510 can't be accessed by the XP Home
computer
> > although the HP4l on the wireless Linksys print server still works . I'm
> > beginning to hate this month's Windows Update. All the pc s use the same
> > version of Zone Alarm Pro for the firewalls
> >
> >
> > "John Beckett"
 wrote in message
> > news:6lcbd11fdquhpmhcu4pke1g6f6bs3pk1de{at}4ax.com...
> >> "Rich Gauszka"  wrote in message
> >> news::
> >>> "tempstorage on 'aspire( 192.x.x.x)'   - the xyz is
missing from the
> >>> computer name as it should say "tempstorage on
'xyzaspire(192.x.x.x)'
> >>> I'm
> >>> not sure what's happening here
> >>
> >> I don't have a fix, but a computer has two names: its normal FQDN and
its
> >> NetBIOS name (which is normally the same). To view:
> >>
> >> My Computer, right-click, Properties, Computer Name, Change, More.
> >>
> >> John
> >>
> >
> >
>
>

--- BBBS/NT v4.01 Flag-5