Windows 98 SE unable to browse network

My network consists of a Win 98SE box (Evelyn), and a Win XP Home SP2
box (Emily) networked through an Actiontec DSL router. For some time
now, I've been unable to browse shared folders on Emily from Evelyn,
getting the infamous "\\Emily is not available. No permission to
access resource" error. I can see both computers in Network
Neighborhood on Evelyn, and I can browse Evelyn's files from Emily
perfectly normally. I'm convinced my network is set up OK, because I
can ping Emily from Evelyn, and execute DOS commands like "Dir" and
"copy" on Emily shares from Evelyn (however, "net use" doesn't work).
This seems to be a fairly wide-spread problem, from what I'm able to
gather on the Net; I've asked for help on this group, but so far have
been unable to solve the problem.
I suspect that a recent or fairly-recent XP update did something to
the permissions which has the effect of preventing a 98 computer from
browsing the XP's shared-out folders, because it used to work from the
time I initially set up the network to sometime this summer. I've
tried setting up identical accounts, with identical passwords, on both
machines to no avail. The "net guest" account on the XP machine
appears to be configured normally. Both computers have Client for
Microsoft Network enabled, as well as File and Print Sharing. The
only protocol on either is TCP/IP.
I did have a drive letter on Evelyn mapped to a share on Emily, which
continued to work despite the browsing problem until I disconnected it
and was unable to reconnect because of not being able to browse Emily.
I did find out how to reconnect this, however, with a registry hack,
so now I do have shares on Emily mapped to drive letters on Evelyn,
letting me continue to do my work. But I still would like to know
what's gone wrong and how to fix it.
I appreciate all the help and suggestions I've received on this group;
if somehow I discover how to fix this somewhere else, I'll be sure to
share it here.
Peter
Peter L. Reader, posting from sunny Portland, Oregon
(E-Mail Removed)
---------------

Just want to try.

1) Windows 98 have to logon with user & password same as Windows Xp logon ID
preferrably with administrator right, if any. If not, create it.

2) If you can ping Evelyn, try to run \\Evelyn_ip_address if there is any
static IP address assigned to Evelyn. Maybe netBIOS can't resolve the PC name.

3) I faced the same situation like you before this. What I do is to
register/create Evelyn controlpanel->system->computername->domain eg domain1.
Then do no. 1
with domain=domain1. (Win XP Professional)

Pls let me know the status.

"Peter L Reader" wrote:

> My network consists of a Win 98SE box (Evelyn), and a Win XP Home SP2
> box (Emily) networked through an Actiontec DSL router. For some time
> now, I've been unable to browse shared folders on Emily from Evelyn,
> getting the infamous "\\Emily is not available. No permission to
> access resource" error. I can see both computers in Network
> Neighborhood on Evelyn, and I can browse Evelyn's files from Emily
> perfectly normally. I'm convinced my network is set up OK, because I
> can ping Emily from Evelyn, and execute DOS commands like "Dir" and
> "copy" on Emily shares from Evelyn (however, "net use" doesn't work).
> This seems to be a fairly wide-spread problem, from what I'm able to
> gather on the Net; I've asked for help on this group, but so far have
> been unable to solve the problem.
> I suspect that a recent or fairly-recent XP update did something to
> the permissions which has the effect of preventing a 98 computer from
> browsing the XP's shared-out folders, because it used to work from the
> time I initially set up the network to sometime this summer. I've
> tried setting up identical accounts, with identical passwords, on both
> machines to no avail. The "net guest" account on the XP machine
> appears to be configured normally. Both computers have Client for
> Microsoft Network enabled, as well as File and Print Sharing. The
> only protocol on either is TCP/IP.
> I did have a drive letter on Evelyn mapped to a share on Emily, which
> continued to work despite the browsing problem until I disconnected it
> and was unable to reconnect because of not being able to browse Emily.
> I did find out how to reconnect this, however, with a registry hack,
> so now I do have shares on Emily mapped to drive letters on Evelyn,
> letting me continue to do my work. But I still would like to know
> what's gone wrong and how to fix it.
> I appreciate all the help and suggestions I've received on this group;
> if somehow I discover how to fix this somewhere else, I'll be sure to
> share it here.
> Peter
> Peter L. Reader, posting from sunny Portland, Oregon
> (E-Mail Removed)
> ---------------
>

On Wed, 27 Oct 2004 02:49:04 -0700, "GW"
<(E-Mail Removed)> wrote:

>Just want to try.
>
>1) Windows 98 have to logon with user & password same as Windows Xp logon ID
>preferrably with administrator right, if any. If not, create it.
Thanks for the suggestions...
Already logging on to both computers with the identical
logon/password...with Administrator rights on the XP box.

>
>2) If you can ping Evelyn, try to run \\Evelyn_ip_address if there is any
>static IP address assigned to Evelyn. Maybe netBIOS can't resolve the PC name.
NetBIOS is not installed on either computer...just TCP/IP. I don't
think there's a problem with the network connections....the fact that
I can browse Evelyn from Emily quite nicely, plus being able to run
DOS level commands on Evelyn such as DIR and COPY using resources on
Emily, makes me think the problem is in Windows somehow.....

>
>3) I faced the same situation like you before this. What I do is to
>register/create Evelyn controlpanel->system->computername->domain eg domain1.
>Then do no. 1
>with domain=domain1. (Win XP Professional)
Doesn't work with XP Home...won't let me set up a domain. When I try
to use user-level permissions on Evelyn, it fails when it can't find
the user list on the domain server (or a domain server, for that
matter).
The only thing I haven't tried is to bilge the whole network and
reinstall from scratch--hardware on up. I have some deadlines facing
me, so won't do that until I get caught up. I can make it work for me
well enough with the drive mapping hack.....
>
>Pls let me know the status.
>
>"Peter L Reader" wrote:
>
>> My network consists of a Win 98SE box (Evelyn), and a Win XP Home SP2
>> box (Emily) networked through an Actiontec DSL router. For some time
>> now, I've been unable to browse shared folders on Emily from Evelyn,
>> getting the infamous "\\Emily is not available. No permission to
>> access resource" error. I can see both computers in Network
>> Neighborhood on Evelyn, and I can browse Evelyn's files from Emily
>> perfectly normally. I'm convinced my network is set up OK, because I
>> can ping Emily from Evelyn, and execute DOS commands like "Dir" and
>> "copy" on Emily shares from Evelyn (however, "net use" doesn't work).
>> This seems to be a fairly wide-spread problem, from what I'm able to
>> gather on the Net; I've asked for help on this group, but so far have
>> been unable to solve the problem.
>> I suspect that a recent or fairly-recent XP update did something to
>> the permissions which has the effect of preventing a 98 computer from
>> browsing the XP's shared-out folders, because it used to work from the
>> time I initially set up the network to sometime this summer. I've
>> tried setting up identical accounts, with identical passwords, on both
>> machines to no avail. The "net guest" account on the XP machine
>> appears to be configured normally. Both computers have Client for
>> Microsoft Network enabled, as well as File and Print Sharing. The
>> only protocol on either is TCP/IP.
>> I did have a drive letter on Evelyn mapped to a share on Emily, which
>> continued to work despite the browsing problem until I disconnected it
>> and was unable to reconnect because of not being able to browse Emily.
>> I did find out how to reconnect this, however, with a registry hack,
>> so now I do have shares on Emily mapped to drive letters on Evelyn,
>> letting me continue to do my work. But I still would like to know
>> what's gone wrong and how to fix it.
>> I appreciate all the help and suggestions I've received on this group;
>> if somehow I discover how to fix this somewhere else, I'll be sure to
>> share it here.
>> Peter
>> Peter L. Reader, posting from sunny Portland, Oregon
>> (E-Mail Removed)
>> ---------------
>>

Try reviewing Microsoft Knowledge Base Article KB190648