From: "Rich Gauszka" 

Nope. That seems the reverse of what I'me seeing ( plus my names are dotless )

\\ipaddress\sharename works but \\servername\sharename doesn't when
connecting to a XP Pro share from XP Home

It was working fine until I did this morning's Windows security update and
now my XP home PC can only connect via ipaddress. It's something I can live
with although I will grouch < maybe next month's 'security' update will
fix
it >


"Geo"  wrote in message
news:42d56477$1{at}w3.nls.net...
> Have you ever tried this fix for a previous issue
> http://www.nthelp.com/50/drag_n_drop_broken.htm
>
> I'm just wondering if that could have something to do with it.
>
> Geo.
>
> "Rich Gauszka"  wrote in message
> news:42d531ec{at}w3.nls.net...
>> After Tuesday's Windows update my XpHome PC can no longer connect to a
> share
>> by computername but only by IPaddr. The two XPpro PCs work ok after the
>> update.
>>
>> I've tried the 'ipconfig  /flushdns' and 'netsh winsock reset' to see if
>> those commands would magically fix anything but unfortunately it didn't
> make
>> a difference
>>
>> the computer name ( XpPro)  I'm trying to connect to is 'xyzaspire' but
> when
>> I connect to the share by IPaddr, explorer shows the share as
>>
>> "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
>>
>>
>
>

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