similar to: problem with win98 and passwords

Has any tried to connect to a samba server while using Win98 beta 2 as a client? I keep getting incorrect username/password errors in the samba log file and am unable to either map a drive or connect to a shared resource. With debug level set to 4 on the samba serve the main error seems to be error in packet at line 129 for cmd=117 (or something like that). If anyone else finds a fix for this,

Hello! First time posting to this list. I recently purchased a Tripp-Lite OMNIPLUS1000LCD from Costco (USA). I have it attached via USB to a Dell computer with Ubuntu 8.04 server (all updates on it). I've gone through a lot of research on google and this list and can't figure out why my UPS will not connect using nut/usbhid-ups. My setup in ups.conf is: ------- [OMNI1000LCD]

I now have the deskjet print printing from my Win98 box. Something in the "hpdeskjet" entry was causing the error of "No machine name found" to appear when I tried to print from Win98. I fixed this by deleting the entry and re-creating it. I also specifically added allowed IP addresses instead of using "all" in the config file. I created a generic text printer

I recently reinstalled Linux on my fileserver (RedHat 7.2), which was running Samba (v 2.2.1a). Now, trying to reconfigure Samba back to its original state (silly me didn't keep a copy of the conf file) I've run into a problem. My win98 machines can't find the Samba server by name, but they can by number. By this I mean: On a Linux desktop, smbclient -L //marvin/ works as

Hi there, I have a somewhat wide experience with samba. I've succesfully installed it as a client as well as a PDC on Windows networks. The last time, however, there has been an issue with the win9x stations. I've setup the Samba server over Linux to act as a PDC for the domain. I use dhcp to assign the network configuration to the hosts, and the only protocol installed on them is

Hi all, I try to explain my strange Samba problem: I've done a linuxbox with Mandrake 8.2 distro; installed Samba 2.2 packages and two printers attached via parallel port: one works with the motherboard built-in parallel port, the other is connected via a pci parallel port card. Both works fine on win2000 clients (and on the linuxbox, too :); on windows 98 clients, both printers are

The subject line says it all really. I'm running Samba 2.0.4.b on FreeBSD, sharing a tree as I normally do (we use samba on about a dozen machines so I'm reasonably familiar with it). This one particular machine is not accessible from Windows NT Workstation 4.0 clients. It works fine for Windows 95 and Windows 98 clients. The machine does not show up in the Network Neighborhood for

I'm a newbie at using Samba. I've been working to allow my Win98 users access to file space on the Linux box. I'm now trying to them access to the Linux printer. The printer works fine within Linux, but when I try to print to it from the Win98 side, I get an error saying unknown device. I've configured the printer as a network printer, it is seen by Network Neighborhood, but I

I have just setup a VPN connection three sites using IPCOP. Everything seems to be talking ok, apart from browsing the network neighborhood. There are no NT/Win2K/XP servers running on any of the sites, all sites are just running win98 pc's using tcp/ip. I have tried configuring all PC's to be on the same workgroup and setup sharing, but still each site can only see the pc's

Hi all! I'm using Samba v2.0.4b with Mac OS X. My Win98 machines are giving me behavior that I'm having difficulty diagnosing: * The server doesn't show up under Network Neighborhood. * Map Network Drive doesn't work with the "netbios name" I specified. I may be confused, but it doesn't work with the "workgroup name", either: \\NETBIOSNAME\SHARE NAME

Has anybody tried to login to a Linux NT domain.. I'm getting password problems.. It used to work fine in Win95 until I went to WIn98 (I guess a big no no....) I tried in network neighborhood and double cliked the Linux machine and I got the prompt for a password on \\newjackswing\ipc$ but no password worked?? any ideas?? George Vieira http://newjackswing.dyn.ml.org

Hi! Just today, I managed to attach my Win98 client at home to my remote network which is controlled by a Linux samba 2.0.5a server. The TCP/IP connection is working just fine, I'm able to access all services like ftp, telnet, ... The Win98 client is connected to the network using the DialUp-Network. The option "log on to remote network" is activated and as far as I can conclude

Sent this one in the other day but did not get a reply! When first time logging into Samba (or share), using an dialup internet modem connection, it seems to take between 50-70 seconds to respond to a Windows 98 request. You can see the request leaving the modem and can count the 50-70 seconds before the modem responds from the Linux Server box. Don't see the same problem if I telnet, ftp or

Hi, I think this is related to Petter Osterlund's post... I have two CYGWIN machines: a Win98 (400 megHz) (with a cable modem) and a Win2K (1.4 megHz) (attached to a token ring network) that I am trying to use rsync with over the Internet... I got things to work for a small directory (150 files. 5 megs). I was using a -azvPu flag with --delete and --modify-window=1 and -e ssh The ssh

All - Client: Win98, first version Server: Linux Mandrake, Samba 2.0.7 I'm trying to setup a Samba server to replace a customer's evil Windows 98 server, and have run into a problem. When used with encrypted passwords, it doesn't work. I tried all of the usual cures, and found that it worked perfectly if I enabled plaintext passwords in Win98. When I switched back to encrypted

Folks, please help... I got Samba 2.0.5a running fine on a RH6.1 system and a Win98 client. I have applied the Win98 registry thing to enable plain text passwords, and smb.conf has a "encrypt passwords = no" in it. It works. I have also enabled domain logons and a small login script, and that works too. I sniffed the network and saw the passwords in clear text during the login process.

I am trying to use Samba between a RedHat Linux 9 system and several Win98 PC's. From the Win98 systems, I can see and access the Linux folders I have made available. I can see the Win98 PCs and their shared directories from the Linux box. Understanding that Win98 requires encrypted passwords, I have set the "encrypt passwords" keyword in the smb.conf file to "yes".

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.

My LAN is running Samba v1.9.18p10 under RedHat Linux v5.2. Using the SMB services are Win95 and OS/2 clients. It's all running fine. I will soon be adding Win98, though, and I understand that there is a question of password encryption. I'm concerned how the encrypted/plain-text communication of password will affect my existing configuration. If I reconfigure Samba to use encrypted

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