Re: Adding Linux machine to existing wireless WinXP network - Heeeelllllp!
From: Andy Fraser (andyfraser31_at_hotmail.com)
Date: 01/31/04
- Next message: gil: "installing on a K6 500 problems...help!"
- Previous message: Lenard: "Re: Boot problem"
- Maybe in reply to: H. Simpson: "Re: Adding Linux machine to existing wireless WinXP network - Heeeelllllp!"
- Next in thread: Crusty Curmudgeon: "Re: Adding Linux machine to existing wireless WinXP network - Heeeelllllp!"
- Reply: Crusty Curmudgeon: "Re: Adding Linux machine to existing wireless WinXP network - Heeeelllllp!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 31 Jan 2004 21:17:00 +0000
Crusty Curmudgeon uttered the immortal words:
These are more random thoughts about the info you posted rather than a
detailed troubleshooting guide. Some of it may help.
> Thanks for the help. I have made some progress, but it seems inconsistent.
> I can now see SOME windows shares from Linux box (but not all-why??). I
> can also see MDKGROUP and "Samba Server (localhost)" from the XP system. I
> also have internet access from the linux box. Network from XP Looks like
> this: _______________________
> NETWORK:
> -MYLANWORKGROUP:
> -John
> -Jane
> -MDKGROUP:
> -Samaba Server (localhost)
> _______________________
Why 2 workgroups? I don't enough about Windows networking to be able to help
with using more than 1 workgroup on a LAN. I've only ever used 1 workgroup
or a domain.
<snip>
> smb.conf follows...
> [global]
> printcap name = cups
> dns proxy = no
> load printers = yes
> default = global
> server string = Samba Server %v
> os level = 20
> log file = /var/log/samba/log.%m
> smb passwd file = /etc/samba/smbpasswd
> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
> max log size = 50
> printing = cups
> workgroup = MDKGROUP
Try setting this to that same workgroup that the Windows machines are using.
> map to guest = bad user
> printer admin = @adm
> encrypt passwords = yes
> security = share
Try setting this to "security = user". It's the default and most common
option.
Make sure all the Windows users have a username and password set up with
smbpasswd so they can connect.
You don't have the "netbios name" parameter set. It should default to the
first part of the hostname. I don't know what the hostname is on your box
and I don't know how SMB on Windows would handle a netbios name of
"localhost" if that's what it's being set to.
You may want to look into the SMB browser settings. I've had problems in the
past with various machines starting browser wars.
Definitely look into setting up Webmin (if you haven't already). Everything
I've learnt about Samba (I've only scratched the surface of what it can do,
just enough to get it working for me) has come from using Webmin then
looking at smb.conf, man smb.conf and a few HOWTOs. Samba isn't hard to set
up but when it's not working it can be tough going. O'Reilly have a whole
book on Samba which helps to demonstrate how complex Samba can get.
Remember to restart Samba if you change anything.
-- Andy.
- Next message: gil: "installing on a K6 500 problems...help!"
- Previous message: Lenard: "Re: Boot problem"
- Maybe in reply to: H. Simpson: "Re: Adding Linux machine to existing wireless WinXP network - Heeeelllllp!"
- Next in thread: Crusty Curmudgeon: "Re: Adding Linux machine to existing wireless WinXP network - Heeeelllllp!"
- Reply: Crusty Curmudgeon: "Re: Adding Linux machine to existing wireless WinXP network - Heeeelllllp!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|