Puzzling Windows NetWork Situation

[Mortis]

Greetings. Ok... here is a situation that has had me going in circles for a couple hours. I am working on a NetWork that has 4 comps (I hope this is not confusing). The main computer is running XP Pro and is not shared to the other comps across the NetWork. The other 3 Comps are running Win2kPro and are Shared to the XP Box and to eachother. Prior to Upgrading the Boxes to SP3 I had to logon to each machine, it required a Logon Name and Pass (according to my settings). However, after upgrading... it no longer required a logon and pass- it auto authorized according to settings in the shares and securities- and nothing changed other than SP3. I have one box left that I have not upgraded and am playing around with it- it does STILL require a logon and pass, but once authorized, it is much faster at being accessed and browsed from the main comp then the others that have been upgraded. Why is this and what can I do to revert the others back... can I do anything at all? Each machine has the Shares, Permissions and Securities set Identically

Let me know if you need further clarification... And Thanks for Replies and Ideas.

Mortis

[Mntsnow]

Hmmm I will have to think about that one Mortis. cause if I log in on One box and have the same user account on the other boxes (same login & password) then mine have Never asked for login name and password. Only time I get prompted for a user name and password is if the box that I'm connecting "to" DOESNT have the account I'm currently logged into on the connecting "from" box in it's share permissions

[Mortis]

Thanks, MtnSnow. Just to clarify a couple things- I have seperate UserNames and Logons for each machine. It is not on a Domain, but they are setup on a workgroup (it is a small home network). With the pre SP3 machine, Once I access and login- Username/password, I can access it again and again without having to login.. until the main machine or preSP3 machine is rebooted. For accessibility security, I trim the permissions and stipulate the securities myself. I am at work now so I cant list what I have and how I have it, but can later... if needed.

I should also mention that I might be doing things a$$ :p backwards ... I have learned most of what I do with networking by trial and error and then reading up about my errors.... hehe. I used to access practicallynetworked.com but dont like the new format (since whats his name left/was fired). I have searched for new network sites but havent found a one-in-all resource that is effective and thorough, InMyOpinion.

Thanks for the Considerations.

Mortis

[Mntsnow]

What you are now discribing is correct behavior. (keeping connectivity until reboot of either machine). If it was different prior to sp3 I cant explain it but what you are now discribing is correct behavior.

[Mortis]

Thanks... However, this behavior was different and is still with one of the Machines. Prior to SP3 installation, I had to logon to the machine with the settings. With the exact settings- nothing changed -and then an install of SP3 the process changed.... which is what I am trying to figure out in my original post. With the 1 machine that has not been upgraded- it is much faster at accessing the network or at being accessed by the Network whether that is logon or browsing. I know it is hard to picture and I am probably doing a pretty slack job of explaining... but- once I upgrade the last machine to SP3, it will exhibit the same behavior (not needing ot logon and slow browsing) just like the other 2 machines did. I did this with each one and the results were/are the same.

Thanks... I will keep reading and trying to figure this out.

Mortis

[Mntsnow]

Maybe during the SP3 upgrade it added this back in?
http://www.xtremepccentral.com/vbforums/showthread.php?postid=1095#post1095

[Mortis]

Greetings and Thanks MntSnow for your ideas and comments... I have 3 of the 4 systems functioning the way I want them. I had never deleted that reg key before so I dont think SP3 put it back in, but I figured it wouldnt hurt to take it out... hehe. So I did and I did notice it speed up several of the machines- except for the last one. Now this is frustrating... it has to be something with that machine- it was the only machine that was existent before I added the other two... meaning- I had set that one up a while ago and networked it with the XP Pro box. So I must have tweaked something or set something that I am not finding right now. The two machines that were added very recently function Great and Fast (as far as network is concerned). The last machine in question does not require a log on and pass (which a logon and pass is wanted) to access the network. But the others upon first access to the network (after a bootup) do... but then at any point I can go in and access them from the main box quickly and they dont hesitate. Where as the StubbornSOB :bunny: of a Box that isnt cooperating does not require a logon and pass ever and whenever I access, it hesitates for 15-20 seconds then gives access... then once I break that connection and re-establish, it lingers and "thinks" again.... whereas the others are instantaneous and dont pause. Grrrrrr. I cant remember any setting, tweak or significant change I would have made to that box that would cause this... but I must have done something.

Oh Well, it will be a tinkering activity when I have time... but I will eventually sort it out.

Thanks Again,
Mortis

EDIT: RESOLVED: Hmmm, I decided to do one last pitch effort- I used system mechanic to go in and delete all old reg keys and TMP Files... this resolved it. It must have had a temp key or reg entry that was holding certain info. Once cleaned, it is now functioning as all the others... go figure ;)

Thanks

[Centurion]

eh - well we all read the book first and then check to make sure we understand it before trying it!


NOT -

thanks for the ? Mortis - I have had mystery problems sometimes and wondered where they related - your continued comments have given me ideas to go back to and check!

C :)

[Mntsnow]

Glad you got it going :)

[Axel]

do any or all of the logins have local administrative rights on their respective PC's?

Additionally - you sound like you're looking for network security that typically requires a domain controller to do consistantly....

You indicate they are all in a workgroup ( which only means they can see each other on the network, not much else ) and not in a controlled domain.

As the root drives on NT machines have a common share on them - I suspect what was happening is that each machine developed a profile for the user once they logged in and stored that profile locally - then when they access that share again - they simply authenticate off the local profile and you're in..... especially if you have administrative rights on the box

you really sound like you want a domain - not a workgroup -

Additionally - are your drives FAT, or NTFS? - that will make a difference as well when it comes to security.

Lastly - which protocol are you running TCP/IP or NETBUI or both?

[Mortis]

Hmm... To answer some of your questions, Axel-
Your presumption abot the User Profiling seems correct... at that time, I did log into all my NTFS machines as Admin (I know, not a good idea :) ) but have since changed that habit now that I am more familiar with my NetWork and its setup.

My wants for a Domain vs Workgroup, I am afraid that I am a simpleton when it comes to Networking. I know enough and do enough to make everything work somehow and securely (according to scans and tests)... but thats where it stops. I tend to struggle through the Trial and Error process first then Read later. I am getting half decent with Home Networks using workgroups, but would be lost with anything more complex, such as the nitty gritty things like domains... I do confuse the perimeters of the two easily when trying to accomplish things.

My drives are mostly NTFS, but do have a few Win98 boxes that are shared out.

I dont run TCP/IP for the workgroup, I use NetBEUI and also have IPX/SPX installed for some older apps and my printer. I dont like using TCP/IP for networking (less secure, IMO), am afraid I am more familiar with NetBEUI and trust its security more. I completely stay away from NetBIOS... but realize I will be more and more forced to become more comfortable/knowledgable with this Protocol.

Thanks for your follow up reply. Things have been running good lately.

In the area of HomeNetworking, I am an old dog. I got used to Networking Win9x platforms and locking them down with settings... now that I run mostly NTFS OS's (all Pro Versions), I have had to learn quite a bit more and am still learing- which is a good thing :) .

Thanks.

[Axel]

let's clear up one lil thing right away - you don't appear to be having an issue "networking" -

this thread probably doesn't belong in this forum - but might easily be move to the OS forum -

your issues are most likely NT domain security issues and have zero to do with the TCP/IP network you have running there -

and that will confuse some -

Building a lil box to be a PDC ( primary domain controller ) will resolve your issues. The box doesn't have to be much - it just has to be capable of running windows 2000 server - so a minimum of a P3 chip with a 10 GB hard drive and a 100BaseT network card would be in order - an old HP Vectra VLi8 550 mHz box would fit the bill and you could probably trip across that at an auction somewhere for a few hundred. ( remember to upgrade the BIOS before you load server - many old system BIOS cannot handle win2k server. )

win2k and XP suck when it comes to system and file security in a workgroup environment. You end up having to build protected shares and other stuff and can't make much use of active directory or policy security setups except on the local machines without a domain controller.

Most IT departments in smaller companies often justify buying a server to be the domain controller when the oldest machine in the office that can run win2k server would do just fine unless you are doing some heavy duty roaming profile work. even then, a good hard drive will often be the only truely needed expense outside of the server OS.

[Mntsnow]

The box doesn't have to be much - it just has to be capable of running windows 2000 server - so a minimum of a P3 chip with a 10 GB hard drive and a 100BaseT network card would be in order -

Ahhem, I run a celly 333 as my PDC and a 6 gig drive (still has over 3gigs freespace) with 256 mem and runs perfectly using Win2K Server SP3 so unless your running a enterprise level domain server there is NO need for a p3 system. I have 14 boxes that authenticate into that box and never have a problem.

edit:

Size 6.3 GB
Space Used 2.5 GB
Space Available 3.8 GB
Percent Used 39%
Percent Available 61%

[Mortis]

What you suggest is more than I want to accomplish for the Home setting.

Thanks for the Input.

[Axel]

I was wondering about that - most people, except Mt Snow of course, don't run full fledged domains at home.....

now watch - 30 people with home domains will post in an hour or so......

[Mntsnow]

lol

[Mortis]

LOL!

However, I spent the better part of the afternoon reading more in depth about what you suggested- I still have a long way to go, but it sounds like fun and a viable alternative. I even have a box that would be perfect- a P2 400 with the bare essentials.

I may be bugging you guys with this stuff in the future ;) .

[Mntsnow]

We'll be here Mortis! That 400 would do a fine job of playing the role of pdc for you