System Admin

Dave Kreskowiak23-Jan-06 5:49

23-Jan-06 5:49

It worked yesterday because the account you used on one machine had the same username and password the other machine recognized. This is because each machine in your workgroup has it's own set of user accounts and passwords.

The only sure-fire way around this is to reconfigure your workgroup LAN setup into a domain environment. That way, every machine in the domain will use a single set of user accounts.

RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

Saksida Bojan23-Jan-06 6:28

Saksida Bojan

23-Jan-06 6:28

I don't know nothing abaout domain. Where can i get some info, What it is, How to set up and What are advantage of domain.

Dave Kreskowiak23-Jan-06 6:44

23-Jan-06 6:44

You can start with the XP Resource Kit. I highly recommend picking it up. It's the best $40 US you'll spend if you want to know how every works in XP.

Here's[^] a real quick introduction to the concepts.

And a little more[^].

RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

Saksida Bojan23-Jan-06 7:10

Saksida Bojan

23-Jan-06 7:10

From the link it seems it requires a client with Windows 2000/2003, I don't have those windows, and i don't want to make my computer a client. This is a home network, and the domain is out of my reach.

Is it possible to set a Username and password without a domain? And if so How?

I am using Windows XP SP2

Dave Kreskowiak23-Jan-06 13:08

23-Jan-06 13:08

Again, you have 2 machines, each with it's own accounts and passwords. Ther eonly way this is going to work WITHOUT a domain is if the account names and passwords match on both machines. If you change the password to an account on one machine, you have to change it on the other. There is no other way around this besides a domain.

RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

Mekong River23-Jan-06 15:43

23-Jan-06 15:43

Both of your computer mush have:

- The same user account name and password.
- The same workgroup name.
- The same IP address network id (but difference host id. Exp: 192.168.1.1 and 192.168.1.2).

Dave Kreskowiak23-Jan-06 17:31

23-Jan-06 17:31

Roath Kanel wrote:
The same user account name and password.

True.

Roath Kanel wrote:
The same workgroup name.

Not true. Both machines can be in completely different workgroups since each machine, not workgroup, maintains its own account database. So long as the usernames and passwords match, workgroup information doesn't matter.

Roath Kanel wrote:
The same IP address network id (but difference host id. Exp: 192.168.1.1 and 192.168.1.2).

Definately not true. The IP address/Network address has nothing to with authentication between two machines.

RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

Mekong River23-Jan-06 17:36

23-Jan-06 17:36

Dave Kreskowiak wrote:
Not true. Both machines can be in completely different workgroups since each machine, not workgroup, maintains its own account database. So long as the usernames and passwords match, workgroup information doesn't matter.

Ok, i agree.

Dave Kreskowiak wrote:
Definately not true. The IP address/Network address has nothing to with authentication between two machines.

It is not for purpose of authentication. But it is in purpose of communication. Is it possible if the first computer ip address is 192.168.0.1 and the second computer is 192.168.1.1?

Dave Kreskowiak24-Jan-06 2:35

Installing an Unsigned Add-in on a Local Computer on a Network

24-Jan-06 2:35

So long as there is a route between the two networks, this is not a problem.

If there is no route, he wouldn't be able to contact the other machine at all. If that was the case he'd never get the login box he says he's getting.

RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

JSadleir22-Jan-06 22:56

JSadleir

22-Jan-06 22:56

Hi System Adminstrators

In a networked environment, how would a network administrator handle an unsigned Excel Add-in that needs to be accessed by several individual computers on the network? Does a network administrator have the ability to create a selfcert.exe type certifcate so that the add-in can be treated as a trusted source and allowed to function on the network? Or would it be necessary to install the Add-in on the C: drives of the relevant users' computers?

I hope this makes sense and isn't too vague

Thanks

Jeremy

Re: Installing an Unsigned Add-in on a Local Computer on a Network

Mekong River12-Feb-06 11:45

workstation autolock after autologin?

12-Feb-06 11:45

JSadleir wrote:
how would a network administrator handle an unsigned Excel Add-in that needs to be accessed by several individual computers on the network?

Just share it from the server machine and import this add-in in an excel.

T1TAN22-Jan-06 11:51

22-Jan-06 11:51

Hi everyone, this is my problem..

I recently got a 24/7 internet (cable) connection, and I'd like to use it 100% by keeping my PC running 24/7, even when I'm away for the weekend. To make it simple: I need to enable autologin to my account, run some apps (for downloading) and then lock the workstation so my roommate can't mess with my personal files.

My OS is WinXP SP2, if that matters at all. Smile | :)

Is there a way to do this without buying some specialized apps?? Every idea is welcome Smile | :)

---
http://sprdsoft.cmar-net.org - We Sprd You Softly
Our site features contents and several images. All of this is very weird.

In the end, war is not about who's right, it's about who's left.

Dave Kreskowiak22-Jan-06 12:47

22-Jan-06 12:47

Set the screensaver to activate after 30 seconds (or whatever you want) and enable the password protection checkbox.

Automating Logon[^] on MSDN.

RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

Mekong River22-Jan-06 14:15

22-Jan-06 14:15

Dave Kreskowiak wrote:
Set the screensaver to activate after 30 seconds

The minimum value is 1 minute (60 seconds) only Smile | :)

T1TAN22-Jan-06 18:33

22-Jan-06 18:33

I'm afraid that's not good enough, we all know that 60 secs is quite a long time, and I need the workstation to lock itself immediately after login. Sigh | :sigh:

Another option would be to run my apps as windows services, but I wouldn't know how to do it properly. D'Oh! | :doh:

---
http://sprdsoft.cmar-net.org - We Sprd You Softly
Our site features contents and several images. All of this is very weird.

In the end, war is not about who's right, it's about who's left.

Dave Kreskowiak22-Jan-06 19:18

22-Jan-06 19:18

Easy enough. Write a little app that P/Invokes the Win32 API function LockWorkStation[^], preferrably in C++. It'll be a very short little app. Put a shortcut to this little .EXE in the Startup folder of the user ID that's going to be logged in.

RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

T1TAN22-Jan-06 19:57

22-Jan-06 19:57

That seems good. Smile | :)

BUT, (there has to be one) I believe this won't be password protected lock then? Since I need to disable login password if I want windoze to autologin. Or, did I get it wrong? D'Oh! | :doh:

---
http://sprdsoft.cmar-net.org - We Sprd You Softly
Our site features contents and several images. All of this is very weird.

In the end, war is not about who's right, it's about who's left.

Dave Kreskowiak23-Jan-06 1:52

23-Jan-06 1:52

Yep, you got it wrong.

Autologon and Locking the workstation will not affect the screen saver. When the screen saver kicks in, the workstation will still be locked. You'll still have to unlock it to use the machine.

RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

Gavin Taylor22-Jan-06 19:55

Gavin Taylor

22-Jan-06 19:55

Following on from what Dave was getting at in the above thread, you could always just create a shortcut under the Explorer startup group to run the command line:

rundll32 user32.dll LockWorkStation

Gavin Taylor
w: http://www.gavspace.com

-- modified at 1:56 Monday 23rd January, 2006

T1TAN22-Jan-06 20:02

22-Jan-06 20:02

This would also work, but my question above still remains: is this really going to secure my PC if I have to disable login passwords in order for autologin to work?? Dead | X|

---
http://sprdsoft.cmar-net.org - We Sprd You Softly
Our site features contents and several images. All of this is very weird.

In the end, war is not about who's right, it's about who's left.

Gavin Taylor22-Jan-06 20:15

Gavin Taylor

22-Jan-06 20:15

Grab a copy of TweakUI[^] and you should be able to automatically set which user you want windows to login as and theres an option to specify a password as well.

Gavin Taylor
w: http://www.gavspace.com

T1TAN22-Jan-06 22:28

22-Jan-06 22:28

I've found some registry keys[^] to do just that (I suppose TweakUI uses them too), thanx for your fast reply Wink | ;-)

These are the keys:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\<br />
<br />
AutoAdminLogon = 1<br />
DefaultDomainName = [Domain name]<br />
DefaultUserName = [User name]<br />
DefaultPassword = [Password]

---
http://sprdsoft.cmar-net.org - We Sprd You Softly
Our site features contents and several images. All of this is very weird.

In the end, war is not about who's right, it's about who's left.

Dave Kreskowiak23-Jan-06 5:46

23-Jan-06 5:46

T1TAN wrote:
I have to disable login passwords in order for autologin to work??

Where was this mentioned???? No one said anything about this. You can't disable login passwords anyway, so I wondering where this came from.

RageInTheMachine9532
"...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

T1TAN23-Jan-06 7:05

23-Jan-06 7:05

Sorry, I was reading a completely irrelevant MSDN article, and things got a bit messed up in my head Blush | :O

---
http://sprdsoft.cmar-net.org - We Sprd You Softly
Our site features contents and several images. All of this is very weird.

In the end, war is not about who's right, it's about who's left.

Mekong River23-Jan-06 15:34