IWETHEY v. 0.3.0 | TODO
1,095 registered users | 1 active user | 1 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New OK, too

Figured out the authentication thing. Remind me to post my SQL Server chamberpot of horrors sometime...

\r\n\r\n

Apparently, a domain user (eg: DOMAIN\\USERNAME) cannot use password authentication. So create a new user. Naturally, "USERNAME", matching "DOMAIN\\USERNAME" isn't clearly distinguished by SQL Server from the domain user. So delete that and create a fresh account and set a password.

\r\n\r\n
\r\n
\r\n$ sqsh -S 192.168.1.40             \r\nsqsh-2.1 Copyright (C) 1995-2001 Scott C. Gray\r\nThis is free software with ABSOLUTELY NO WARRANTY\r\nFor more information type '\\warranty'\r\nPassword: \r\n1> \r\n
\r\n
\r\n\r\n

...and queries work.

\r\n
--\r\n
Karsten M. Self [link|mailto:kmself@ix.netcom.com|kmself@ix.netcom.com]\r\n
[link|http://kmself.home.netcom.com/|http://kmself.home.netcom.com/]\r\n
What part of "gestalt" don't you understand?\r\n
[link|http://twiki.iwethey.org/twiki/bin/view/Main/|TWikIWETHEY] -- an experiment in collective intelligence. Stupidity. Whatever.\r\n
\r\n
   Keep software free.     Oppose the CBDTPA.     Kill S.2048 dead.\r\n[link|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html|http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html]\r\n
New OT: how is DOMAIN\\USER kind of login supported in SAMBA
client?

I've got bitten once trying to acces a share protected that way. Had to do it from a Windows machine in the end.
--

Less Is More. In my book, About Face, I introduce over 50 powerful design axioms. This is one of them.

--Alan Cooper. The Inmates Are Running the Asylum
New RTFM
Samba is trivial to set up with swat. The difficulties are in the bizarre syntax and confusing wording of the configuration file. Of course, if you go into Samba without understanding LAN Manager (the most brain dead NOS of all time, and so something that is easy to understand), then you will get out of it what you took into it.

The only vitally important parameters are security (share, user, domain) and OS level (for NetBIOS browser elections). The actual problems happen with synchronizing users on the domain vs. UNIX. That is simple with smbadduser. If you remember that ALL LAN Manager networking is really peer-to-peer, you've got it licked.

There was a parallel in the days of NT 3.51 Server, which was really the same binary thing as NT 3.51 Workstation. By editing the registry, you could convert WS into Server or even a DC - really, the same thing as security=share vs. security=user vs. security=domain. It's really quite trivial. Oh that was a hateful operating system.

Bring it on, game boy.
-drl
New Consider winbind.


Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Blog]
New Client. Client. Client. Damn it.
--

Less Is More. In my book, About Face, I introduce over 50 powerful design axioms. This is one of them.

--Alan Cooper. The Inmates Are Running the Asylum
New As Petah said...
Look into winbind. You can set up Windows users as Unix users, in the style of username = "MYDOMAIN+arkadiy". You can then log on as that user on the unix box, and winbind will hand off the authentication on the share to your Windows domain controllers/AD.

Many fears are born of stupidity and ignorance -
Which you should be feeding with rumour and generalisation.
BOfH, 2002 "Episode" 10
     SQL/Server / SQLAGENT / Running by hand - (broomberg) - (12)
         One possible hint - (kmself) - (8)
             Don't see how it applies - (broomberg)
             Works - (broomberg) - (6)
                 OK, too - (kmself) - (5)
                     OT: how is DOMAIN\\USER kind of login supported in SAMBA - (Arkadiy) - (4)
                         RTFM - (deSitter) - (3)
                             Consider winbind. -NT - (pwhysall)
                             Client. Client. Client. Damn it. -NT - (Arkadiy) - (1)
                                 As Petah said... - (tseliot)
         sp_start_job may do the trick - (ChrisR) - (2)
             Thanks - (broomberg) - (1)
                 Probably the best way... - (ChrisR)

bash#_
56 ms