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.
>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.
>
[quoted text clipped - 33 lines]
>> preader@pacifier.com
>> ---------------
Try reviewing Microsoft Knowledge Base Article KB190648