Win XP doesnt see samba share, but can connect to it.
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Win XP doesnt see samba share, but can connect to it.
I have samba configured. I know it works because I can get into it from my windows machine by using the address:
From there the samba server asks for the username and password like normal and works fine. What I want to know is why my windows XP machine wont see the samba hare when there set to be on the same workgroup and what not.
Here's what seems to work well for my little network: (WinXP Pro, Win2k Pro workstations). I think there is a registry tweak that has been mentioned several times before in the forums here for XP to work with Samba. I don't remember it though..
writeable = yes
path = /home/public
force directory mode = 775
force group = users
force create mode = 775
comment = Public Stuff
create mode = 775
directory mode = 775
Go to http://192.168.0.1 to manage your Netgear switch (I think that should work). See if your Linux box shows up as a listed device. If it doesn't, that may be your problem. Making your Linux box master of the local domain (just edit the appropriate line in smb.conf and type "service smb restart") may resolve that issue, but it also may prevent the boxes from connecting altogether.
Bear in mind that you can simply create a shortcut to \\lin.uxb.oxe.sip\ in "My Network Places" and not worry about why WinXP doesn't see your Linux box in the Network Neighborhood.
well.. when I try to go to http://192.168.0.1 I get nothing. Heres how my networks set up .. so youget an idea what Im workin with. I have a Linksys router doing PPPoE authentication to the DSL modem. Then I have a my 1st linux computer connected to the router (theres other poeples computers directly attached to the router, thats why we have one). This 1st machine is doing IP forwarding/masquerading, and DHCP on the 2nd nic. The 2nd nic is creating the 192.168.2.0/24 subnet. The 1st linux box is connected to the switch along with the other nix box and the win XP machine.
But I still dont know why I cant get this crap workin.. I might just have to go with the link plan.... if that works.
In my experience, a Netgear router that does not list your computer may "hide" it from other machines on the network. You can usually fix this by reserving an IP address on the router. To do this, use must access the router setup - usually from http://192.168.0.1 or http://192.168.0.254 or the like (the first or last IP address on your network).
Beyond that, your network situation is beyond my experience level. Good luck!
Put this in your smb.conf file and restart the smbd and nmbd service
remote announce 255.255.255.0
or whatever your netmask is for your xp and linux boxes
please check my spelling on announce, seam to be a little tired.
after that you should see the linux box, if not, do you have the firewal setup on your linux box. Also, you have encryption enabled on your linux box, after you see the computer, unless you have things setup correctly then your gonna have problems, but hopefully not.
Also, do you know what machine is the domain master browser?
Well what's happening is the machines on your network from time to time have an election on who will manage this list of computers on the network, and if there are none or if there are two master browsers then some problems may occurr. Not so much if your systems aren't configured. So, what you have to ask yourself, is which computer is mostly on? If this is a windows box then it is quite easy, sort of. You would do this if it is a windows box that you want as the master browser ALL the time.
goto your Start menu and click Run. Type REGEDIT and hit ENTER
goto this key:
and click on parameters, you should see two keys, IsDomainMaster and MaintainServerList
If you doubleclick on both you set them to Yes
Both of them
If it is the Linux box you want to set as the domain master browser all you need to do it put these entries in the smb.conf file
yeah I entered all that stuff into my smb.conf file. Then I restarted the file server machine, and then after that was booted, I restarted the windows machine. But for some reason the the XP machine still cant see the nix box. I want teh nix box to be the domain master.. so that I dont have to f*ck withthe registry and stuff.
nah theres no fire wall on the internal linux machine. I have ipforwarding disabled as well. I dont know if that has anythign to do with it though. When I do the find computer... the samba server does appear... and I can connect to it and what not. But it still wont show up directly... in the Network neighborhood.