Dreaded Win7 0x80070035 with Samba

Login or Register for Dates, Times and to Reply

 
Thread Tools Search this Thread
Special Forums Windows & DOS: Issues & Discussions Dreaded Win7 0x80070035 with Samba
# 1  
[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 05:21 PM..
# 2  
Could you please post your samba config? If the problem occurred suddenly: did you try rolling back to an earlier restoration point (I don't know the English word...) on the client? Can you access other services within your network? Is there a firewall on the samba server? And what OS is it?
This User Gave Thanks to chmod666 For This Post:
# 3  
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.
# 4  
Something in Win7 might be broken. Your conf looks good and is working anyway, so I'd try to repair the system (repair install via the Win CD). Sorry I couldn't help any more.
This User Gave Thanks to chmod666 For This Post:
# 5  
SOLVED, FOR THE MOMENT!

Taking a close look at the error dumps when windows diagnostics failed, I noticed it was looking at port 445 and ONLY port 445... So I commented out this line, allowing samba to use the ports it thinks appropriate:
Code:
# smb ports = 139

...and the boss' computer was miraculously able to connect again.

For the moment, anyway. It's teased me before by working briefly then dying, and there was no reason for it to suddenly start refusing to use port 139 after using it for months. Let's hope this sticks.
# 6  
That's weird... But as long as it's working Smilie
This User Gave Thanks to chmod666 For This Post:
# 7  
Even though this is a few months old, you might still be interested in a possible solution. I have a similar problem between my Win7 VM and my Kubuntu host. To fix it, I just have to restart smbd before starting Win7. I use the following command:

sudo restart smbd
This User Gave Thanks to ThomasMcA For This Post:
Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #74
Difficulty: Easy
NeXTStep was based on the original BSD operating system.
True or False?

9 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. UNIX for Dummies Questions & Answers

samba

hi, i have 2 raids connected via 2 servers to a third server with a third raid. the first 2 export via nfs to the third so that the third has all the data viewable on it. previously i was able to then use samba to export to our macs. i don't recall anything changing, but now i can't view... (0 Replies)
Discussion started by: user23
0 Replies

9. 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

Featured Tech Videos