Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I have tried to solve this problem about 2 weeks and search around on the Internet, but still can't solve this problem.
Now, i have a Linux Samba in RedHat 9.2. I have a group of PC workstation including Win 95,98,2000,XP and Linux. There is no problem for Win 98,2000,XP and Linux to connect the Samba server except Win95.
I find that about 1/3 of Win 95 workstation can connect to the Samba server, and 2/3 of Win 95 can't. But the specification of the Win 95 PC are the same.
I tried to find the solution by reinstall the NIC driver, use the 'net use' command to connect the server, reset the samba, but the problem still here.
How could i solve this problem, have any suggestion that i can do??
Here is my smb.conf.
workgroup = mygroup
server string = Samba Server
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
wins support = yes
# 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
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
; preserve case = no
; short preserve case = no
# Default case is normally upper case for all DOS files
; default case = lower
# Be very careful with case sensitivity - it can break things!
; case sensitive = no
template shell = /bin/false
winbind use default domain = no
security = share
guest ok = yes
guest account = upload
[homes]
comment = Home Directories
browseable = no
writeable = yes
Distribution: Slackware, CentOS. Red Hat Enterprise Linux
Posts: 216
Rep:
If my memory servers me correctly, there was at one time a issue with Win95 and password encryption (or lack there of) when Service Release 2 was issued. Are all your Win95 the same release?
hi,
thanks for your reply.
Yes, the version of the group of Win 95 are all come from the same version. But some of them can connect, others can't.
But in fact, i can ping the Samba server IP in all win 95 PC.
Distribution: Slackware, CentOS. Red Hat Enterprise Linux
Posts: 216
Rep:
Very strange. The fact you can ping the Samba server means that Win95 TCP/IP stack is working correctly, so the problem is definitely related the NetBIOS functions. The next thing to check is that the Client for Microsoft Networking is installed. You might try deleting it if it's installed on the problem workstations, then reboot and reinstall it. This has fixed problems for me in the past. Also turn of file sharing and see if you can see the Win95 machines from the Samba server.
Very strange. The fact you can ping the Samba server means that Win95 TCP/IP stack is working correctly, so the problem is definitely related the NetBIOS functions. The next thing to check is that the Client for Microsoft Networking is installed. You might try deleting it if it's installed on the problem workstations, then reboot and reinstall it. This has fixed problems for me in the past. Also turn of file sharing and see if you can see the Win95 machines from the Samba server.
Thanks for your reply. I also think that it is the NetBIOS problem. After i have read your message, i try to remove the TCP/IP setting and reinstall the NIC driver, and all Protocol. But the problem still here.
I also try to install a new samba version in another server. The problem still here, then this problem is not because of the samba verison.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.