Sponsored Content
Special Forums Windows & DOS: Issues & Discussions Dreaded Win7 0x80070035 with Samba Post 302601383 by Corona688 on Thursday 23rd of February 2012 02:59:51 PM
Old 02-23-2012
The server is Linux. Its firewall is presently disabled.

Everything else works with perfection, including other things hosted on the server. Just not samba file shares. It's presently using winscp as an ugly workaround. The Win7 machine refuses to acknowledge its existence there. It sees other Windows machines but not the Linux one.

I can't bring the Windows client to an earlier restore point. I don't even know what I'd be trying to undo, anyhow.

Code:
###############################################################################
######## START OF GLOBAL SETTINGS #############################################

[global]
workgroup = WORKGROUP
netbios name = MECGENTOO
#client ntlmv2 auth = yes
#client lanman auth = yes
#ntlm auth = yes
#lanman auth = yes

smb ports = 139

invalid users = "Cap User"

# Map Windows users to UNIX users here
username map = /etc/samba/smbusers


# Uncomment this logging level for login debugging
# log level = 3 auth:10 passdb:5

# All connnecting Windows clients must present a valid username/password
security = user

# Accounts with no password can login
null passwords = yes

encrypt passwords = yes

# The UNIX account 'nobody' is used for guest logins
guest account = nobody

# Administrators login as root
admin users = root

# Tell samba to serve WINS.
wins support = yes

# This would tell it to be a WINS client.
# wins server = 192.168.0.41

# Give it control over network browsing
local master = yes
os level = 99
domain master = yes
preferred master = yes


# This should allow addresses 192.168.0.1-192.168.0.127 to use samba,
# while "hosts deny = All" prevents all others.
hosts allow = 192.168.0.0/255.255.255.128 127.

# Deny all hosts except those we know
hosts deny = All

# 10.1.1.0/255.255.255.0
# hosts allow = 192.168.0. 10.1.1. 127.

# Limit samba to the first network card
interfaces = lan

load printers = no
#printing = cups
#printcap name = cups

######## END OF GLOBAL SETTINGS ###############################################
###############################################################################

###############################################################################
######## START OF SHARE SETTINGS ##############################################

[Archive]
comment=Old or unsorted or backup files
path=/opt/mecgentoo-shared/Archive
create mask = 0660
directory mask = 2770
writeable=yes

...and so on. There's lots more different shares.

The 'hosts allow' is completely intentional. Random clients that aren't recognized by our DHCP server will get IP addresses > 128, which will prevent them from talking to our SAMBA server. Only office computers that our DHCP server has static addresses assigned to will be able to get into SAMBA.

The computer in question has .18 on the wired and .19 on the wireless, so is definitely allowed no matter what.

Did I mention that every other client except this computer still works? Even our network scanner still works.

---------- Post updated at 01:33 PM ---------- Previous update was at 12:39 PM ----------

There were no Windows updates installed between the time this Win7 client was able to connect and when it suddenly started refusing to. None whatsoever.

---------- Post updated at 01:59 PM ---------- Previous update was at 01:33 PM ----------

Had a suggestion to restart the Workstation and/or Computer Browser services.

Attempting to stop the Computer Browser service gets "Error 1061: The service cannot accept control messages at this time".

Attempting to stop the Workstation service gets exactly the same thing.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Need Samba Help

Hi, I am very new to Unix, do know some RedHat linux. I am wanting to install samba on my unix machine. Not sure where to start, any help would be very much appreciated. Thanks, Chris Lewis (4 Replies)
Discussion started by: lewy33
4 Replies

2. UNIX for Dummies Questions & Answers

can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC?

Hi Gurus can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC? regards, Israel. (9 Replies)
Discussion started by: iga3725
9 Replies

3. Solaris

samba issue: one samba share without password prompting and the others with.

Hi All, I've been trying to configure samba on Solaris 10 to allow me to have one share that is open and writable to all users and have the rest of my shares password protected by a generic account. If I set my security to user, my secured shares work just fine and prompt accordingly, but when... (0 Replies)
Discussion started by: ideal2545
0 Replies

4. Linux

Unable to ping Linux guest from win7 host

Hi, I am using win7 on my PC and installed VMware on it on which i am running linux I am unable to ping my linux guest from my win machine, but i can ping my windows host from linux guest : Below is my system configuration Linux root@localhost ~]# ifconfig eth0 Link... (9 Replies)
Discussion started by: chander_1987
9 Replies

5. UNIX and Linux Applications

Samba config for Win7 clients

Hi Guys, Kindly advise what options/settings needed in smb.conf to support win7. currently we are experiencing slow connection issues from our recently upgraded win7 from XP to our Samba server ver. 3.0.33-3.7.el5_3.1 (1 Reply)
Discussion started by: RobertG
1 Replies

6. Proxy Server

Unable to access Samba share with Ubuntu on Win7

I have an issue with my Samba share - I am unable to write to it, edit a file or rename a folder etc within Windows. I am using Windows 7 and Ubuntu 12.04 and this is my Samba config. I can connect to the /sylius directory no problem (no password required), but I cannot save to it. Is... (3 Replies)
Discussion started by: crmpicco
3 Replies

7. UNIX for Advanced & Expert Users

Cp freezing from Seagate HDD to Win7

Hello all, Earlier I had a mac book and created a HFS+ file system on Seagate 1 TB external HDD, copied around 200 GB content. Now, I have a Windows 7 machine and wanted to copy the HDD contents to this new machine. Tried using MacDrive10 to mount HFS+ file system in Windows. Mouting is fine and... (1 Reply)
Discussion started by: matrixmadhan
1 Replies

8. Windows & DOS: Issues & Discussions

Forwarding wmv video directly to Dreamscene [WIN7]

So, I finally got around to getting Dreamscene to work with my Win 7 (64bit) Laptop. The only thing I find quite annoying, is that I have to "right click" a video file (.wmv/.mpg) and select "Set a Background" each time I want to change the video file. Is there a way to 'directly forward' a... (1 Reply)
Discussion started by: pasc
1 Replies
cupsaddsmb(8)							    Apple Inc.							     cupsaddsmb(8)

NAME
cupsaddsmb - export printers to samba for windows clients SYNOPSIS
cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] -a cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] printer [ ... printer ] DESCRIPTION
cupsaddsmb exports printers to the SAMBA software (version 2.2.0 or higher) for use with Windows clients. Depending on the SAMBA configura- tion, you may need to provide a password to export the printers. This program requires the Windows printer driver files described below. OPTIONS
cupsaddsmb supports the following options: -H samba-server Specifies the SAMBA server which defaults to the CUPS server. -U samba-user[%samba-password] Specifies the SAMBA print admin username which defaults to your current username. If the username contains a percent (%) character, then the text following the percent is treated as the SAMBA password to use. -a Exports all known printers. Otherwise only the named printers are exported. -h cups-server[:port] Specifies a different CUPS server to use. -v Specifies that verbose information should be shown. This is useful for debugging SAMBA configuration problems. SAMBA CONFIGURATION
cupsaddsmb uses the new RPC-based printing support in SAMBA 2.2.x to provide printer drivers and PPD files to Windows client machines. In order to use this functionality, you must first configure the SAMBA smb.conf(5) file to support printing through CUPS and provide a printer driver download share, as follows: [global] load printers = yes printing = cups printcap name = cups [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = no printable = yes [print$] comment = Printer Drivers path = /etc/samba/drivers browseable = yes guest ok = no read only = yes write list = root This configuration assumes a FHS-compliant installation of SAMBA; adjust the [printers] and [print$] share paths accordingly on your system as needed. MICROSOFT POSTSCRIPT DRIVERS FOR WINDOWS
The base driver for Windows 2000 and higher is the Microsoft PostScript driver, which is available on any system running Windows 2000 or higher in the %WINDIR%SYSTEM32SPOOLDRIVERSW32X863 folder for 32-bit drivers and %WINDIR%SYSTEM32SPOOLDRIVERSX643 folder for 64-bit drivers. The CUPS printer driver is preferred over the Microsoft driver since it supports the page-label, job-billing, and job-hold-until options fully on all printers. However, currently only Windows 2000 and higher is supported by the Microsoft driver, so you will also need to get the Adobe driver to support Windows 95, 98, and Me clients. The Adobe and Microsoft drivers for Windows 2000 are identical. Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the /usr/share/cups/drivers/x64 directory exactly as named below: [Windows 2000 and higher] ps5ui.dll pscript.hlp pscript.ntf pscript5.dll Note: Unlike Windows, case is significant - make sure that you use the lowercase filenames shown above, otherwise cupsaddsmb will fail to export the drivers. CUPS POSTSCRIPT DRIVERS FOR WINDOWS
cupsaddsmb can use the CUPS v6 PostScript printer driver for Windows, which is available for download from the CUPS web site. The CUPS printer driver is preferred over the Adobe and Microsoft drivers since it supports the page-label, job-billing, and job-hold-until options fully on all printers. However, currently only Windows 2000 and higher is supported by the CUPS driver, so you will also need to get the Adobe driver to support Windows 95, 98, and Me clients. Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the /usr/share/cups/drivers/x64 directory exactly as named below: [Windows 2000 and higher] cups6.inf (from www.cups.org) cups6.ini (from www.cups.org) cupsps6.dll (from www.cups.org) cupsui6.dll (from www.cups.org) ps5ui.dll (from your Windows system) pscript.hlp (from your Windows system) pscript.ntf (from your Windows system) pscript5.dll (from your Windows system) Note: Unlike Windows, case is significant - make sure that you use the lowercase filenames shown above, otherwise cupsaddsmb will fail to export the drivers. ADOBE POSTSCRIPT DRIVERS FOR WINDOWS 95, 98, AND ME cupsaddsmb can use the Adobe PostScript printer driver for Windows 95, 98, and ME, which are available for download from the Adobe web site (http://www.adobe.com). The Adobe driver does not support the page-label, job-billing, or job-hold-until options. Once you have installed the driver on a Windows system, copy the following files to the /usr/share/cups/drivers directory exactly as named below: [Windows 95, 98, and Me] ADFONTS.MFM ADOBEPS4.DRV ADOBEPS4.HLP ICONLIB.DLL PSMON.DLL Note: Unlike Windows, case is significant - make sure that you use the UPPERCASE filenames shown above, otherwise cupsaddsmb will fail to export the drivers. KNOWN ISSUES
Getting the full set of Windows driver files should be easier. SEE ALSO
smbd(8), smb.conf(5), http://localhost:631/help http://www.cups.org/windows/ COPYRIGHT
Copyright 2007-2011 by Apple Inc. 25 July 2007 CUPS cupsaddsmb(8)
All times are GMT -4. The time now is 07:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy