Sponsored Content
Special Forums Windows & DOS: Issues & Discussions Dreaded Win7 0x80070035 with Samba Post 302601332 by Corona688 on Thursday 23rd of February 2012 12:19:42 PM
Old 02-23-2012
[SOLVED?] Dreaded Win7 0x80070035 with Samba

I have a Win7 machine which is connected to a perfectly ordinary Samba share. Suddenly, it has started refusing to connect to it with error 0x80070035 -- "the network path was not found". Attempting to login with its IP address \\192.168.x.x does not work either. When I attempt to diagnose the problem, it helpfully tells me that there's nothing there to connect to, which I know is complete baloney. I can ping the IP address. I can ping the server by hostname. I can even ping it by its SAMBA name. It just never tried.

Checking in the firewall settings, "file and printer sharing" was disabled. Enabling it made zero difference. I also made sure 'network discovery' and 'core networking' weren't firewalled.

I set the NTLM authentication level to 2 in the registry as many things suggest(being Win7 Home, Microsoft helpfully removed the control panel applet to manage that properly), this also made no difference.

I've uninstalled any antivirus and firewall products, and disabled the firewall on the server itself for the time being.

Enabling NETBIOS under WINS settings inside TCP/IP advanced settings made no difference.

I've updated to a newer version of Samba(inconveniencing the office as everyone needed to put their passwords back in) to no effect.

Another identical(same model, same OS, same software, same apparent configuration) Windows 7 machine works absolutely fine, just like this one did before it threw this fit.

I've added the following lines to smb.conf at the suggestion of various sources:
Code:
netbios name = myservername
client ntlmv2 auth = yes
client lanman auth = yes
ntlm auth = yes
lanman auth = yes

...to no effect.

Hunting on the internet for this error finds dozens of users screaming about the problem and dozens of conflicting solutions, none of which work for me.

The server logs show absolutely zero indication that the PC in question has ever even tried to access the samba share. Meanwhile all our Windows XP clients still work fine, as well as the identical Windows 7 machine across the room -- identical model, identical OS, identical apparent settings, on the exact same local network.

Does anyone have any insights?

---------- Post updated at 10:59 AM ---------- Previous update was at 10:37 AM ----------

Resetting Windows Firewall to defaults (then re-enabling file+printer sharing, etc) made no difference.

Deleting and re-installing the network device made no difference.

netsh winsock reset made no difference.

---------- Post updated at 11:19 AM ---------- Previous update was at 10:59 AM ----------

Running a long cable from her PC to the same switch the server is plugged into made no difference.

Last edited by Corona688; 02-23-2012 at 04:21 PM..
 

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. However, currently only Windows 2000 and higher is supported by the Microsoft driver, so you will also need to get the Adobe driver to sup- port 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. 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 COPYRIGHT
Copyright 2007-2013 by Apple Inc. 8 July 2013 CUPS cupsaddsmb(8)
All times are GMT -4. The time now is 03:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy