|
| | | 
Forum Advisor
 
Group: Advisor
Last Login: 7/23/2008 9:45 PM
Posts: 310, Visits: 792 |
| I have a home network with Windows XP Pro SP2 and current updates, and a Windows 98 with all available updates. The XP Pro machine is my main computer, with the 98 machine as the one to play with. I keep my ICQ, Yahoo, MSN and AOL clients running on that one to keep those off of this machine, and backup copies of most of what I've downloaded and purchased software too. Each machine can see each other just fine, as I can place a file in the shareddocs folder on either machine and have the other one see it in there just fine. So far, so good.
Well, here's where it gets weird...
If I double click on the Network Neighborhood icon on the 98 machine, I can see three things in this folder: Entire Network, the name of the 98 machine, and the name of the XP Pro machine. If I double click on the 98's icon, it takes me to the shareddocs folder. Still so far, still so good. I can see files that I've placed in there from both the 98, and the XP machine. Now...if I double click on the XP machine's icon from the 98 machine, I immediately get a prompt stating: "Enter Network Password" "You must supply a password to make this connection." I don't get this prompt doing it the other way around, from the XP machine to look into the 98's shareddocs folder. Still with me here?
What's interesting is that I've (as much as I hate to say this) never entered a password for networking OR when I installed XP Pro OR when I set up 98. In other words, when I boot my XP machine, it goes straight to the desktop. No password is needed. Same thing for the 98 machine.
Since I'm the only one here and another account is not necessary for either machine, there is no need for a password, because there's only one user...me.
So the question is, what could possibly be the default password for networking, or where in the OS or registry can show me what it is? Could there also be a "universal password" for this type of situation for the first time, and then later change it? Universal password may not be a good term, but I think you see what I'm getting to here.
It's just an annoyance for the 98 machine to ask for a network password, while the XP machine does not. Other than that, file sharing between the two works well.
I hope that I've my scenario as clear as I possibly can. Sometimes it's hard to put into words what I see on my screen, so feedback or ideas will be GREATLY appreciated! 
___________________________________________________
 |
| |
| | | Senior Forum Advisor
Group: Senior Advisor
Last Login: 12/1/2007 4:53 AM
Posts: 200, Visits: 117 |
| i will try and say this correct. as i kinda remember it reelated to me.
windows 98 used "share level" protection, and XP uses "user level" protection (and shared). in XP if someone is a user on it, they can access whatever users are allowed to access on it.
In 98 , whatever you have set for shared, and accessed via a password, can be accessed by anyone, wether they are a user on that computer or not, as long as there is a password for that resource, they will have to use the password to get into it.
now myself i MUCH prefer the shared level access, where nobody GETS to become a user or guest into my computer, and MUST go through a password process to access any data on said computer.
Vrses
the XP which has users, can allow full complete control of the computer via users (not just data) , and complicates sharing resources, with both shared AND user level access. this method fills up the registry with users , and adds more overhead, and is not simple, although IF you can figure it out, it would have a higher level of security, if you cant figure it out, and control it correct, then its a hackers dream server :-).
ahh enough ranting.
on win98 set up resources that you share in the disk properties or wherever, and set a read only or full access passwords, then when you go to access that area with your other computer, put that password in, and tell XP to SAVE that password info. untill you change the password on the win98 resource , it will be remembered on your xp computer.
you will not be able to access any resources on the 98 computer, untill you set them to be shared, and put a password in, that is why you will get a "cant acess //your other computer/resource/f" because its not yet shared, which is a good thing.
i find that anytime i change the password, its good to link the computers together , change any of the win98 passwords , and access that data imediatally with same said password on the xp computer.
so you might use that method to set up a win98 share, find what you want to access, bring up its properties, put in the password, then on the xp computer try and acess that resource , and put in the password then, that way you got the password data synced.
also, WHY was it so EASY to waltz right into your XP computer? :-) ahh security where would we be without 17 layers of it.
-----------------------------------
This Poster knows NOTHING about VISTA , if your issue was VISTA related , then it don't apply. |
| |
| | | Senior Forum Advisor
Group: Senior Advisor
Last Login: 12/1/2007 4:53 AM
Posts: 200, Visits: 117 |
| other endless discussion:
here we do basically the same thing, the win98 computer is "exposed" to the net, and firewalled, and available to hackers to blow up at will if they can :-)
and my precious main computer is subbed off of that , and is disabled totally from being any kind of server for anyone or anything, so all the server items have been shut off or removed, or blow up as best as possible, then the workstation service is disabled UNTIL any workstation type access is ever needed.
acsess to the other computer uses this batch, put on a button.
you might like it ??
----------------------------
start /B "Attempt connect sound" C:\Desk\batch\wav.exe C:\WINDOWS\Media\AppSounds\directccO.wav start /B "Open up net folder" explorer "C:\Documents and Settings\me2know\NetHood" net start workstation
rem this starts the normally off workstation, set on manual then turned on via this command.
C:\Desk\batch\pv.exe -qkf wav.exe >nul
rem this thing, (unnessisary) stops the trying to connect sound, as soon as connection actually occurs start /B "Connected sound" C:\Desk\batch\wav.exe C:\WINDOWS\Media\AppSounds\RnappO.wav
-------------------------------
also you can add in a DIR of the folder with a errorlevel, to check if the connection was completly made, but that gets more complex, most of this batch is not so much connection, but sounding off what is occuring.
-----------------------------------
This Poster knows NOTHING about VISTA , if your issue was VISTA related , then it don't apply. |
| |
| | |
Forum Advisor
Group: Advisor
Last Login: 7/23/2008 9:45 PM
Posts: 310, Visits: 792 |
| Thank you! You've given me some GREAT study material
Since I have the week of Christmas off from work, I'll be relaxing in front of the soft, warm glow of my fire... Aw, I can't lie! I'll be in front of my PC's! I'm too much of a Geek (and proud of it) to spend it elsewhere.
I'll look into what level of shares both machines have, and start from there. If all else fails, I have a contact out in Montana that'll walk me through it step by step.
Happy Holidays!
___________________________________________________
|
| |
|
|
