similar to: Logging in from Win98

There have been several postings about this phenomenon and we too fell into it when we introduced Win98 clients onto the network. Somewhere on the web I found the answer: By default Win98 sends passwords to a server encrypted, and by default SAMBA compiles with encrypted passwords switched off. Therefore the password one types in from a Win98 client is received by SAMBA in an encrypted form.

If samba isn't authenticating win98 clients, esp. if you get a password request for IPC$, try editing the win98 registry. Go to HKEY_LOCAL_MACHINE\ System\CurrentControlSet\Services\VxD\VNETSup and add a new DWORD entry. Name it EnablePlainTextPassword and set it to 1. The capitalization of VNETSup may be different but the rest is exactly as I found it on my system. After a reboot of the

Does anyone Know the procedure for Windows 2000 workstation, in order to not encrypt passwords. What I needed is something similar to the transcription I make below that works for windows nt4 and 98. Thank's Emanuel Duarte (Portugal) ********************************** This should take care of the "clear text password" problemsyou've encountered: For Win 98 (To enable

Recently Microsoft introduced some network improvements which made it impossible to connect to Samba without using encrypted passwords. There is a way-around for NT4.0 (SP3) by changing a registry entry. This has been published by Microsoft in their knowledge-base. With WIN95 OSR2.1 and the vredir patch (vredir.vxd and vnetsup.vxd dated June, 2nd 1997 or later) the behaviour is very similar to

Hello, My question is the same as "Windows 98 Passwords" in your Samba FAQ replacing Windows 98 with Windows 2000. What is the registry to be modified to enable Plain Text Password with Windows 2000 ? I tried HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VxD\VNETSUP as in Windows 98 and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters as in NT4 but none work.

I found these articles that talk about the oplock_break problem (specifically they are related to problems with word97): http://support.microsoft.com/support/ntserver/serviceware/nts40/e9msge2bc.asp http://support.microsoft.com/support/kb/articles/q163/5/25.asp Basically they say: either apply sp3 on the winnt client or disable oplock on nt server But they don't say anything about win9x,

Dear All: I have a problem about the printer server of samba. I instlled samba on IRIX 6.5. When I print file from PC, it asked me passwd first and any passwd is not valid. I change the /HKEY_LOCAL_MACHINE/System/CurrentControlSet/Service/Vxd/VNETSUP and add DWORD value as 1. Then after I enter my passwd, it does not show error information, but I still can not get anything from printer, somtime I

Hallo Liste Derzeit mache ich meine ersten Gehversuche mit Linux (SuSE). Bis jetzt habe ich in einem kleinen Netzwerk f?r meine Tauchschule vier Rechner betreut. Einer davon war WinNT-4.0 Server und Arbeitsplatz zugleich. Nachdem ich nicht mehr bereit bin, mich mit dem w?chentlichen "blue screen" und dem monatlichen Neuinstallieren von NT abzufinden, bin ich derzeit beim Umsteigen auf

Hi, I had similar problems with Samba and speed. To begin with, I thought it was a Samba problem, and spent a lot of time stuffing around with smb.conf Then, just to make certain it was Samba and not a generic TCP/IP problem, I tried ftp'ng a big file to and from the Samba server from W95. Speed was only 20 k/sec - about 2% of the expected speed of a 10-Base-T network. Same for FTP'ng

How can we set up the policy working for different users (belonging to diffe rent groups) on the same win98 machine? Win98 looks up the netlogon share on our Samba server in security level = us er, domain logons = yes. It parses the config.pol file, but the only group policy defined that applie s to ANY user logging on is the one for Users group I added in Policy Editor .. eirvine

Hi. I have Samba set up to serve W95 PCs. Kids "log in to the network" using their Unix password. Students get their Unix home dir mounted as network drive X: when login is successful. This all happens on IP subnet 192.168.1.1/24 So far, so good. We are thinking about adding another IP subnet - say 192.168.2.1/24. Of course, the two subnets will be connected with a router. It

>From: "Eddie Irvine" <eirvine@tpgi.com.au> >To: <samba@samba.anu.edu.au> >Subject: Logging on to the network - one samba, two subnets. >I have Samba set up to serve W95 PCs. Kids "log in to the >network" using their Unix password. Students get their >Unix home dir mounted as network drive X: when login is >successful.> >This all happens

I have a question about Win98 and Samba. Is there a registry fix similar to the WinNT plaintext passwd that needs to be performed? Win95, and WinNT can see Linux via Netbios, but the same machine, running Win98 cannot see the Linux box. I am running the most current version of Samba. The WinNT box can see the 98 machine fine. Does anyone have any experience with this? Please let me know if

I'm writing because I had a problem with Samba, while installing it on some of our computers with Windows 98 (beta 3). We have an internal network not accessible from the outside, in which we use the sending in the clear (I.E. not encrypted) of the access passwords to Samba running on a Sun machine with Unix Solaris OS. We use unencrypted passwords because Windows 95 doesn't support

I just can't seem to get this working... I've moved a number of OS level DLLs and VXDs over from WIN98... HERE'S WHAT I GET: # wine --dll shell,shell32,shlwapi=n EXPLORER.EXE fixme:ddeml:DdeNameService (1,49195,0,1): stub fixme:ddeml:DdeNameService (1,49191,0,1): stub fixme:ddeml:DdeNameService (1,49193,0,1): stub fixme:process:SetProcessShutdownParameters (00000002, 00000000):

Problem: -------- On the client mascines I get the msg: "The account is not authorized to log in from this station." This has bugged me for days now, so I am posting this sloution around varius places on the net... Analysis: --------- from a round of analysis by Jamz Boman B.Sc (Jamz@Boman.com), Toby Corkindale (tjcorkin@steadycom.com.au) Andreja Zivkovic (zivkotech@ozemail.com.au) at

Hi all, i'm trying to run carmageddon 2 on my slackware 12.1 using wine but i have no success. I installed the game from original CD just fine and when i try to run it i get the conf window but then wine crashes. Following the details of crash. I can give much details if needed. I googled for a while but found nothing interesting. Thanks a lot fixme:vxd:VXD_Open Unknown/unsupported VxD

Hello all, I have just installed samba on my linux machine, but failed to browse Linux resources from a Windows2000 machine. But if i changed the 'security = user' to 'security = share', i can browse linux from Windows2000 box, i don't think i have problems with the connections. I guess there must be something wrong with the password authentication methods. I read the

check the output of : echo "\n" | testparm -vv | grep signing and echo "\n" | testparm -vv | grep protocol for my the default is : client max protocol = NT1 but i dont use signing. but i "think" you need to set the client signing = manadatory and client max protocol = SMB2 ( from man smb.conf ) but if anyone know this better on the list, please

Problem: No login names/password combinations are vaild. Vague idea of problem area: Authentication (unencrypted/encrypted mismatch?) Details: Network: WinXP connected to DSL giving IP masquerading to the LAN. Win2000 computer I log on most of the time (named Tyler-Durden). Redhat 8.0 computer (named CheeZe) that's running samba (I don't know how to