Any have any clue why I'd get a bluescreen crashwhen accessing a Linux server on my home network? Just going to network and browsing.. even if I leave the window open and walk away..WIN7 will crash after several minutes..

I take it you're talking about accessing a Samba share... it wouldn't be the first time an new MS OS has had problems with Samba. Anybody else have trouble like this?

Yes, that's exactly it :)I have been using the identical setup with Vista for quite some time and had no issues at all..

I am having a similar problem, W7 is stable running just fine but about 5 min after logging on to my samba share I get blue screen for a flash. All I am able to read is a fatal error occurred and it does a memtest. It started doing this yesterday(1/18) for no apparent reason.I have had this same setup for 2 years and have had XP, OSX, Vista, and Ubuntu all use it with no problems.

I am using Samba too (Ubuntu server 8.10/Samba 3.23), butIhaven't had this problem. I have both Vista (32 and 64 bit) and Windows 7 clients.I would start by making sure you have the latest version of Samba (I believe it's 3.2.3 on Ubuntu).

Yup, I have the exact same problem. And I AM running the latest version of SAMBA. well i tried to edit this for more detail. But it won't take.There are many many more issues with networking in win7. The situation is probibly the worst I have ever seen in any OS, ever.

Without intention of being for or against Windows.. I must say.. Keep in mind this is a beta.. there will be bugs to be worked out.

I too am experiencing Win7(as a VirtualBox 2.1.0 guest)crashing while trying to access a Samba share running on Sidux. I can connect to the shared folder no problem. However, when I try to access a sub-folder the Win7 screen goes black with various colored pixels filling the screen, no BSOD. I have had to power off the virtual machine as it is totaly unresponsive. This has happened twice so far. The first time Win7 would not complete a restart. It would hang at the glowing Windows logo. After another power off it would still not completly load. I restarted again, Windows suggested I run the repair process to fix my installation. I allowed it to run and it suggested a system restore which I allowed. Afterwards Win7 successfully loaded.I tried accessing the Samba share again, and again same thing happened as described above. This time however, I was able to complete a restart. Now, I am not seeing in Network either the XP machine or the Samba server machine. I only see my Win7 (only the Media Devices icon) and my router. After my first issue I was able to see the XP and Samba computer along with the Win7 computer and Media Devices.I can ping both the XP and Samba servers by IP and by name (my hosts file has entries for both computers).

To update: A restart of Win7 brought back the other computers in Network (Samba server and XP). I connected to both XP shares and browsed for about 5 minutes, opening several files. No problems. I then connect to my Samba share and browsed and opened several files. After 6 minutes I stopped momentarilytoopen a file on my host. At that point Win7 screen went black withthe multicolored pixels.I have just restarted Win7 with no problems, all computers show up in Network as expected. Sure seems like a Samba / Win7 issue.

I have tested Samba share in both user mod and share mod and it work fine so can you post your samba.conf file so that I can help you.it should be located at /etc/samba/samba.conf on your linux server.PeaceI use samba 3.2.3 on mandriva linux 2009

Fred 666Thanks for the reply and off to help! I am pasting my Samba config file as you requested. I am using version 3.2.5-4## Sample configuration file for the Samba suite for Debian GNU/Linux.### This is the main Samba configuration file. You should read the# smb.conf(5) manual page in order to understand the options listed# here. Samba has a huge number of configurable options most of which # are not shown in this example## Some options that are often worth tuning have been included as# commented-out examples in this file.# - When such options are commented with ";", the proposed setting# differs from the default Samba behaviour# - When commented with "#", the proposed setting is the default# behaviour of Samba but the option is considered important# enough to be mentioned here## NOTE: Whenever you modify this file you should run the command# "testparm" to check that you have not made any basic syntactic # errors. # A well-established practice is to name the original file# "smb.conf.master" and create the "real" config file with# testparm -s smb.conf.master >smb.conf# This minimizes the size of the really used smb.conf file# which, according to the Samba Team, impacts performance##======================= Global Settings =======================[global]## Browsing/Identification #### Change this to the workgroup/NT-domain name your Samba server will part of netbios name = kensidux workgroup = WOLFDEN# server string is the equivalent of the NT Description field server string = %h server (Samba %v)# Windows Internet Name Serving Support Section:# WINS Support - Tells the NMBD component of Samba to enable its WINS Server# wins support = no# WINS Server - Tells the NMBD components of Samba to be a WINS Client# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both; wins server = w.x.y.z# This will prevent nmbd to search for NetBIOS names through DNS. dns proxy = no# What naming service and in what order should we use to resolve host names# to IP addresses; name resolve order = lmhosts host wins bcast#### Networking ##### The specific set of interfaces / networks to bind to# This can be either the interface name or an IP address/netmask;# interface names are normally preferred; interfaces = 127.0.0.0/8 eth0# Only bind to the named interfaces and/or networks; you must use the# 'interfaces' option above to use this.# It is recommended that you enable this feature if your Samba machine is# not protected by a firewall or is a firewall itself. However, this# option cannot handle dynamic or non-broadcast interfaces correctly.; bind interfaces only = yes#### Debugging/Accounting ##### This tells Samba to use a separate log file for each machine# that connects log file = /var/log/samba/log.%m# Cap the size of the individual log files (in KiB). max log size = 1000# If you want Samba to only log through syslog then set the following# parameter to 'yes'.# syslog only = no# We want Samba to log a minimum amount of information to syslog. Everything# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log# through syslog you should set the following parameter to something higher. syslog = 0# Do something sensible when Samba crashes: mail the admin a backtrace panic action = /usr/share/samba/panic-action %d####### Authentication ######## "security = user" is always a good idea. This will require a Unix account# in this server for every user accessing the server. See# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html# in the samba-doc package for details.# security = user# You may wish to use password encryption. See the section on# 'encrypt passwords' in the smb.conf(5) manpage before enabling. encrypt passwords = true# If you are using encrypted passwords, Samba will need to know what# password database type you are using. passdb backend = tdbsam obey pam restrictions = yes# This boolean parameter controls whether Samba attempts to sync the Unix# password with the SMB password when the encrypted SMB password in the# passdb is changed. unix password sync = yes# For Unix password sync to work on a Debian GNU/Linux system, the following# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for# sending the correct chat script for the passwd program in Debian Sarge). passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .# This boolean controls whether PAM will be used for password changes# when requested by an SMB client instead of the program listed in# 'passwd program'. The default is 'no'. pam password change = yes########## Domains ############ Is this machine able to authenticate users. Both PDC and BDC# must have this setting enabled. If you are the BDC you must# change the 'domain master' setting to no#; domain logons = yes## The following setting only takes effect if 'domain logons' is set# It specifies the location of the user's profile directory# from the client point of view)# The following required a [profiles] share to be setup on the# samba server (see below); logon path = \\%N\profiles\%U# Another common choice is storing the profile in the user's home directory# (this is Samba's default)# logon path = \\%N\%U\profile# The following setting only takes effect if 'domain logons' is set# It specifies the location of a user's home directory (from the client# point of view); logon drive = H:# logon home = \\%N\%U# The following setting only takes effect if 'domain logons' is set# It specifies the script to run during logon. The script must be stored# in the [netlogon] share# NOTE: Must be store in 'DOS' file format convention; logon script = logon.cmd# This allows Unix users to be created on the domain controller via the SAMR# RPC pipe. The example command creates a user account with a disabled Unix# password; please adapt to your needs; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u########## Printing ########### If you want to automatically load your printer list rather# than setting them up individually then you'll need this# load printers = yes# lpr(ng) printing. You may wish to override the location of the# printcap file; printing = bsd; printcap name = /etc/printcap# CUPS printing. See also the cupsaddsmb(8) manpage in the# cupsys-client package.; printing = cups; printcap name = cups############ Misc ############# Using the following line enables you to customise your configuration# on a per machine basis. The %m gets replaced with the netbios name# of the machine that is connecting; include = /home/samba/etc/smb.conf.%m# Most people will find that this option gives better performance.# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html# for details# You may want to add the following on a Linux system:# SO_RCVBUF=8192 SO_SNDBUF=8192# socket options = TCP_NODELAY# The following parameter is useful only if you have the linpopup package# installed. The samba maintainer and the linpopup maintainer are# working to ease installation and configuration of linpopup and samba.; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &# Domain Master specifies Samba to be the Domain Master Browser. If this# machine will be configured as a BDC (a secondary logon server), you# must set this to 'no'; otherwise, the default behavior is recommended.# domain master = auto# Some defaults for winbind (make sure you're not using the ranges# for something else.); idmap uid = 10000-20000; idmap gid = 10000-20000; template shell = /bin/bash# The following was the default behaviour in sarge,# but samba upstream reverted the default because it might induce# performance issues in large organizations.# See Debian bug #368251 for some of the consequences of *not*# having this setting and smb.conf(5) for details.; winbind enum groups = yes; winbind enum users = yes# Setup usershare options to enable non-root users to share folders# with the net usershare command.# Maximum number of usershare. 0 (default) means that usershare is disabled.; usershare max shares = 100#======================= Share Definitions =======================[homes] comment = Home Directories browseable = no# By default, the home directories are exported read-only. Change the# next parameter to 'no' if you want to be able to write to them. read only = yes# File creation mask is set to 0700 for security reasons. If you want to# create files with group=rw permissions, set next parameter to 0775. create mask = 0700# Directory creation mask is set to 0700 for security reasons. If you want to# create dirs. with group=rw permissions, set next parameter to 0775. directory mask = 0700# By default, \\server\username shares can be connected to by anyone# with access to the samba server.# The following parameter makes sure that only "username" can connect# to \\server\username# This might need tweaking when using external authentication schemes valid users = %S# Un-comment the following and create the netlogon directory for Domain Logons# (you need to configure Samba to act as a domain controller too.);[netlogon]; comment = Network Logon Service; path = /home/samba/netlogon; guest ok = yes; read only = yes; share modes = no# Un-comment the following and create the profiles directory to store# users profiles (see the "logon path" option above)# (you need to configure Samba to act as a domain controller too.)# The path below should be writable by all users so that their# profile directory may be created the first time they log on;[profiles]; comment = Users profiles; path = /home/samba/profiles; guest ok = no; browseable = no; create mask = 0600; directory mask = 0700[printers] comment = All Printers browseable = no path = /var/spool/samba printable = yes guest ok = no read only = yes create mask = 0700# Windows clients look for this share name as a source of downloadable# printer drivers[print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no# Uncomment to allow remote administration of Windows print drivers.# Replace 'ntadmin' with the name of the group your admin users are# members of.; write list = root, @ntadmin# A sample share for sharing your CD-ROM with others.;[cdrom]; comment = Samba server's CD-ROM; read only = yes; locking = no; path = /cdrom; guest ok = yes[files] comment = My_Documents path = /media/common/My_Documents writable = yes ;guest ok = yes# The next two parameters show how to auto-mount a CD-ROM when the# cdrom share is accesed. For this to work /etc/fstab must contain# an entry like this:## /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0## The CD-ROM gets unmounted automatically after the connection to the## If you don't want to use auto-mounting/unmounting make sure the CD# is mounted on /cdrom#; preexec = /bin/mount /cdrom; postexec = /bin/umount /cdrom

Right off the bat I would suggest that your workgroup name and that your netbios name should be the same !!!That's should fix it.Good luck

Fred Thanks for taking the time to review my config file.The netbios name entry is used so Windows clients can "see" my linux server on the network. Otherwise, I do not believe my linux machine would show up in the Network folder on a Windows client. I do not have DNS or WINS configured, so netbios is my onlymethod for name resolution on my network.Is that how you have your Samba configured, with the netbios and workgroup names the same? Is the name of your Samba server the same as the workgroup?

Ken Wolf said:Fred Thanks for taking the time to review my config file.The netbios name entry is used so Windows clients can "see" my linux server on the network. Otherwise, I do not believe my linux machine would show up in the Network folder on a Windows client. I do not have DNS or WINS configured, so netbios is my onlymethod for name resolution on my network.Is that how you have your Samba configured, with the netbios and workgroup names the same? Is the name of your Samba server the same as the workgroup? Yes Those two should be the same if they are not your are asking for trouble ;)Why I don't know exactly, but hey it work for me all the time. and when those two are not the same I only have trouble.

I gave your suggestion a go, changed the netbios name to be the same as my workgroup. Restarted samba. Win7 was shut down during the changes, by the way. For the heck of it I brought up my WinXP SP3 virtual machine. Sure enough in Network I saw the new computer with the name of my Workgroup. I browsed the Samba share for about 10 minutes with no problem. Shut down XP and fired up Win7.With Win7 running I see in Network the new computer with my workgroup name (also still see the original computer name, but that will disappear eventually). I began browsing at 10:19:31pm it is now 10:30:00 and counting with no crash.Dunno what to say, except for what ever reason making the change you suggested apparently works. I will continue to test, but seems to be working just fine now.Thanks a bunch Fred!

That seems to have fixed the issue, although I'd suggest it's a bandaid solution, since this configuration difference has no effect on other Windows versions..that being said.. I can now access the samba share in peace!! Thanks!!

I was hoping that this might solve my similar issue but it doesn't. I amd getting the BSOD when browsing a NAS share ona Synology DS107. I'm assuming it must be a Linux Samba share because of all the similar issues posted around but when I change the serb=ver name to be teh same as the workgroup name I still get the BSOD after about 7-8 minutes.

Having the same issue here. I've reported it on the hardware board also as it seemed as though it might be something related to specific NIC drivers (only broadcom and one other I've seen it reported on). However it appears to be related to something else at this point.Regardless adjusted my netbios setting on samba also and giving that a shot now (I'll post later in about 15-20mins or more as to whether or not it helps).Also for reference since the BSOD does indeed flash away quickly. The error I was seeing was a 0x00000007E (give or take a couple 0's) with relation to tdx.sys failure.

Still having the same issue as beforealso to further note samba version:[root@server2 ~]# /usr/sbin/smbd -VVersion 3.0.28a-0.fc8I haven't bothered to update the version on my Fedora 8 tower since this is the first time it's given me even an single ounce of trouble (thus I'm certain this is win7 related solely). I'm presuming win7 has some flakey issue with accessing samba network shares (as others have stated it isn't exactly hard to imagine). XP ME 98se 95 and the like all work fine to access it.Anyone by any shred of chance have further insight to this?

I assume you are running some type of anti-virus software. Have you tried temporarily disabling it (or even better, uninstalling it). A lot of different forums reports problems with various anti-virus packages (I have seen Norton, Avast and NOD mentioed).In some cases, upgrading to the lates beta (anti-virus that is) seemed to have an effect.

Kjetil Samuelsen said:I assume you are running some type of anti-virus software. Have you tried temporarily disabling it (or even better, uninstalling it). A lot of different forums reports problems with various anti-virus packages (I have seen Norton, Avast and NOD mentioed).In some cases, upgrading to the lates beta (anti-virus that is) seemed to have an effect.I took off my AV awhile ago (namely the day after installing Win7 aka as soon as it gave me grief).I'm presuming as of this point due to the tdx.sys error which seems to be the case with most of us who've seen this error it would appear to be related to some new MS driver that's been added into the network area of the OS.

It seem that this is an issue of both drivers and anti-viruspackages. For some it helps to uninstall or upgrade the AV package, for others it helps to replace the network drivers.I have found a few posts that may be of help to some of the people with problems:http://community.norton.com/norton/board/message?board.id=Win7Beta&thread.id=180http://blog.tombushby.com/tag/tdxsys/http://forums.overclockers.com.au/showthread.php?t=747892http://www.raneri.it/blog/eng/index.php/2009/01/15/avast-antivirus-causes-bsod-on-windows-7-beta/

I had the same problem, Windows7 crashing when connecting to SAMBa drive, it turned out to be AVG* Free virus I had install and working for several weeks with WIN7, however yesterday it auto updated and had the problem of crashing appear, I had to Un-install AVG8, and also do some manual removing on the registry for AVG8 and then it worked, everything was solved, and by the way Vista also has the same problem.Vista64 WIndows7-64Any way MS should not allow a software tool crash the entire OS, just not a good sign.Please Fix stability of the OS

Kjetil Samuelsen said:It seem that this is an issue of both drivers and anti-viruspackages. For some it helps to uninstall or upgrade the AV package, for others it helps to replace the network drivers.I have found a few posts that may be of help to some of the people with problems:http://community.norton.com/norton/board/message?board.id=Win7Beta&thread.id=180http://blog.tombushby.com/tag/tdxsys/http://forums.overclockers.com.au/showthread.php?t=747892http://www.raneri.it/blog/eng/index.php/2009/01/15/avast-antivirus-causes-bsod-on-windows-7-beta/Tried just about everything known to man on this one already. I did a ton of searching around the other night. Both the included driver in win7 for broadcom and the newest one off broadcom's website don't work to prevent the BSOD issue with tdx.sys. Taking out the AV does not help either (did that already as I mentioned already). The tdx.sys error occurs whenever mapping a linux (samba) network share. As sure as if I asked it to 5mins or less later I get a tdx.sys BSOD error on my screen.I certain can not wait until Microsoft weighs in on this as to how this managed to be missed (one post I read suggests the previous beta didn't have this problem, until the public beta build went out). Considering what I've been reading thus far we should be seeing some sort of hotfix release soon enough I'd hope (as this issue wasn't present before, by a couple reports).

pj29 said:I had the same problem, Windows7 crashing when connecting to SAMBa drive, it turned out to be AVG* Free virus I had install and working for several weeks with WIN7, however yesterday it auto updated and had the problem of crashing appear, I had to Un-install AVG8, and also do some manual removing on the registry for AVG8 and then it worked, everything was solved, and by the way Vista also has the same problem.Vista64 WIndows7-64Any way MS should not allow a software tool crash the entire OS, just not a good sign.Please Fix stability of the OSInteresting, did not know vista had this issue as well. Also I manually went through the registry and removed any AVG keys/entries as suggested/you had done, and well about 10+mins up thus far with a samba share mapped (tempting BSOD/death eh?).I'll post again and update on whether or not this fixes things too - definitely not holding my breath on this one (tick tick tick tick.... awaiting a BSOD).

Well as of this point I think I can safely confirm pj29's answer was the solution on this one. Removing the erroneous reg entries AVG left behind (great uninstaller mind you, leaving behind shortcuts in the start menu and dud reg entries...) seems to have fixed things. Basically had to go through and delete out any AVG entries I could in the registry (there were only two or three windows wouldn't allow to be deleted).I definitely share the sentiment that MS has to get some stability issues ironed out here. No single Application should be able to go crashing the OS in this manner (esp even after the app has been uninstalled...... ?). Needless to say no BSOD with a tdx.sys error yet in about 30+mins of having my samba share mounted and also playing a video file over LAN off it - sufficent to say I think this is fixed then now.

Avast! definitely seems to be the culprit. Disabling doesn't do anything to help, it has to be completely removed, not 100% sure if all the registry entries need to be removed or not but I did it anyway.Any suggestions on what to use for AV?