I know this is a little off topic (not as usual, dammit!), but I figure at least one of y'all can handle this one.
I have tried to configure my CentOS4.4 Plus desktop for samba sharing with the VMWare Windows that runs on it. However, no matter what I've done so far, I can't get the Windows to recognize this machine as a legitimate network destination.
Here's my samba config file:
[root@mhullrichter shared]# cat /etc/samba/smb.conf
# Global parameters
[global]
server string = Samba Server
security = SHARE
log file = /var/log/samba/%m.log
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = /etc/printcap
dns proxy = No
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
cups options = raw
[homes]
comment = Home Directories
read only = No
browseable = No
[public]
comment = Data
path = /home/mark
force user = mark
force group = users
read only = No
guest ok = Yes
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
It passes testparm, the smb daemons are up and running:
[root@mhullrichter shared]# psg smbd
root 2751 1 0 11:44 ? 00:00:00 smbd -D
root 2752 2751 0 11:44 ? 00:00:00 smbd -D
I noticed that neither the nmbd nor winbindd daemons are running - dunno why, the startup showed [ OK ].
But in the Windows, it can see my machine but can't connect to it - what am I missing?
Mark Hull-Richter Linux Kernel Engineer (949) 680-3082 - Office (949) 680-3001 - Fax (949) 632-8403 - Mobile mhull-richter@datallegro.com mailto:mhull-richter@datallegro.com www.datallegro.com http://www.datallegro.com
On 3/23/07, Mark Hull-Richter mhull-richter@datallegro.com wrote:
I have tried to configure my CentOS4.4 Plus desktop for samba sharing with the VMWare Windows that runs on it. However, no matter what I've done so far, I can't get the Windows to recognize this machine as a legitimate network destination.
I think the one thing you might be missing is a "workgroup" configuration. My global section looks like this:
[global] workgroup = workgroup server string = CentOS Samba Server printcap name = /etc/printcap load printers = yes cups options = raw log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = no template shell = /bin/false password server = None username map = /etc/samba/smbusers winbind use default domain = no
The workgroup of the windows machine and the centos machine have to match. The default workgroup on windows is "mygroup" IIRC. Note also that I don't have a "security" setting but I don't think that makes a difference.
I noticed that neither the nmbd nor winbindd daemons are running – dunno why, the startup showed [ OK ].
You might want to find out why. I don't think winbindd matters, but nmbd could be important.
On Fri, 23 Mar 2007 15:14:54 -0400, Mark Hull-Richter wrote:
But in the Windows, it can see my machine but can't connect to it - what am I missing?
When you say "can't connect", what exactly do you see? For example, if you enter
\machinename\homes or \IPaddress\homes
what message do you get from Windows?
Akemi
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Akemi Yagi Sent: Friday, March 23, 2007 1:12 PM To: centos@centos.org Subject: [CentOS] Re: Samba config for Windows on VMWare
When you say "can't connect", what exactly do you see? For example,
if
you enter
\machinename\homes or \IPaddress\homes
what message do you get from Windows?
If I open my entire network, go to Micro$oft networks, Workgroup and click on my samba server, I get this:
If I go to map the network drive, when I get to the server, it grays out the OK button and shows nothing.
If I map it directly, like \mhullrichter\homes, I get this:
I also tried \mhullrichter\mark, which is works with smbclient on the host itself (but not from Windows), I get this:
It's like the host is visible, but not connectible.
PS: Here is what my smb.conf file now looks like, per Bart's suggestion (almost):
[root@mhullrichter samba]# cat smb.conf # Global parameters [global] workgroup = WORKGROUP server string = CentOS Samba Server security = SHARE printcap name = /etc/printcap log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No template shell = /bin/false password server = None username map = /etc/samba/smbusers winbind use default domain = no idmap uid = 16777216-33554431 idmap gid = 16777216-33554431 cups options = raw
[homes] comment = Home Directories read only = No browseable = No
[public] comment = Data path = /home/mark force user = mark force group = users read only = No guest ok = No
[printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No
I don't really care about the printers (they actually work better from the Windows side), but this is annoying. I must be overlooking something. BTW, I also added user mark to the smbusers file, so I'm lost here....
On 3/23/07, Mark Hull-Richter mhull-richter@datallegro.com wrote:
Please do not send html email or images to the list.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Jim Perrin Sent: Friday, March 23, 2007 1:30 PM To: CentOS mailing list Subject: Re: [CentOS] Re: Samba config for Windows on VMWare
On 3/23/07, Mark Hull-Richter mhull-richter@datallegro.com wrote:
Please do not send html email or images to the list.
I saw - useless.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Akemi Yagi Sent: Friday, March 23, 2007 1:12 PM To: centos@centos.org Subject: [CentOS] Re: Samba config for Windows on VMWare
When you say "can't connect", what exactly do you see? For example,
if
you enter
\machinename\homes or \IPaddress\homes
what message do you get from Windows?
When I try to connect through the network tree, I get "\Mhullrichter is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The network path was not found."
If I try to map it, using "\<hostname><anything-else>", I get "The network path \<hostname><whatever> could not be found."
Sorry about the html (actually, it was rtf, but you couldn't rtf content... :-).
Mark Hull-Richter wrote:
I know this is a little off topic (not as usual, dammit!), but I figure at least one of y’all can handle this one.
I have tried to configure my CentOS4.4 Plus desktop for samba sharing with the VMWare Windows that runs on it. However, no matter what I’ve done so far, I can’t get the Windows to recognize this machine as a legitimate network destination.
Here’s my samba config file:
[root@mhullrichter shared]# cat /etc/samba/smb.conf
# Global parameters
[global]
server string = Samba Server
security = SHARE
security=SHARE is for old school win95 networks, with global passwords on each share, I'd avoid that entirely.
use `security=USER`, then read up on smbpasswd. create linux user accounts for each Windows user (same username as they log onto Windows with), then use smbpasswd to set their Samba password to match their Windows login password. Samba can't use their Linux password as SMB networking and Linux use completely different password hashes.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of John R Pierce Sent: Friday, March 23, 2007 2:28 PM To: CentOS mailing list Subject: Re: [CentOS] Samba config for Windows on VMWare
security=SHARE is for old school win95 networks, with global passwords on each share, I'd avoid that entirely.
use `security=USER`, then read up on smbpasswd. create linux user accounts for each Windows user (same username as they log onto Windows with), then use smbpasswd to set their Samba password to match their Windows login password. Samba can't use their Linux password as SMB networking and Linux use completely different password hashes.
Okay, but (I had to have a but in there), I did not set up the Windows account, and it has a space, and a hyphen, in it (Mark Hull-Richter). Does that work on Linux, or should I go to the trouble of making a new Windows account with a simple name, transferring all the settings and files and so on, etc.?
Okay, but (I had to have a but in there), I did not set up the Windows account, and it has a space, and a hyphen, in it (Mark Hull-Richter). Does that work on Linux, or should I go to the trouble of making a new Windows account with a simple name, transferring all the settings and files and so on, etc.?
What networking style did you set up for the vmware client, and how is iptables configured on the host?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Jim Perrin Sent: Friday, March 23, 2007 3:23 PM To: CentOS mailing list Subject: Re: [CentOS] Samba config for Windows on VMWare
What networking style did you set up for the vmware client, and how is iptables configured on the host?
Hmm, you're either dazzling me with your brilliance or baffling me....
The vmware client is using a bridged Ethernet adapter (meaning same as the host, I think).
Here's iptables -L:
Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere
Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT) target prot opt source destination
Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:5353 ACCEPT udp -- anywhere anywhere udp dpt:ipp ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh REJECT all -- anywhere anywhere reject-with icmp-host-prohibited
Hope that's what you were asking for, 'cuz I'm not too familiar with any of this stuff....
Since they're on the same machine, I wouldn't expect it to be so much hassle....
On Fri, 23 Mar 2007 18:49:29 -0400, Mark Hull-Richter wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Jim Perrin Sent: Friday, March 23, 2007 3:23 PM To: CentOS mailing list Subject: Re: [CentOS] Samba config for Windows on VMWare
What networking style did you set up for the vmware client, and how is iptables configured on the host?
Hmm, you're either dazzling me with your brilliance or baffling me....
Both :-)
The vmware client is using a bridged Ethernet adapter (meaning same as the host, I think).
If it is bridged, the client connects "directly" to the outside world. You would need to give a unique IP to your Windows.
Akemi
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Akemi Yagi Sent: Friday, March 23, 2007 4:08 PM To: centos@centos.org Subject: [CentOS] RE: Samba config for Windows on VMWare
If it is bridged, the client connects "directly" to the outside world. You would need to give a unique IP to your Windows.
Isn't there some way for a host to communicate with different parts of itself? If I run the smbclient on the host, it works fine - it acts sort of like ftp. I don't know if there's a Windows analog, but it seems that with at least different ports or something, it should be possible.
Otherwise, the VMWare Server virtual machines are completely isolated from their hosts and thus essentially worthless if any kind of data sharing is desired (like here), except via USB drives and/or CD/DVDs.
Is there another solution for data sharing between Linux and Windows on the same machine (with Linux being the native host OS)? Doesn't WINE do something like this?
Expecting the impossible, as usual, I suppose....
Mark Hull-Richter spake the following on 3/23/2007 4:46 PM:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Akemi Yagi Sent: Friday, March 23, 2007 4:08 PM To: centos@centos.org Subject: [CentOS] RE: Samba config for Windows on VMWare
If it is bridged, the client connects "directly" to the outside world. You would need to give a unique IP to your Windows.
Isn't there some way for a host to communicate with different parts of itself? If I run the smbclient on the host, it works fine - it acts sort of like ftp. I don't know if there's a Windows analog, but it seems that with at least different ports or something, it should be possible.
Otherwise, the VMWare Server virtual machines are completely isolated from their hosts and thus essentially worthless if any kind of data sharing is desired (like here), except via USB drives and/or CD/DVDs.
Is there another solution for data sharing between Linux and Windows on the same machine (with Linux being the native host OS)? Doesn't WINE do something like this?
Expecting the impossible, as usual, I suppose....
I think that is part of the vmware-tools, at least with a windows host and linux virtuals, I have gotten it to work. It is somewhere in the docs.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Scott Silva Sent: Friday, March 23, 2007 4:51 PM To: centos@centos.org Subject: [CentOS] Re: Samba config for Windows on VMWare
I think that is part of the vmware-tools, at least with a windows host
and
linux virtuals, I have gotten it to work. It is somewhere in the docs.
It's part of the VMWare Workstation ($189) but not the Server (free), and even the Server discussion forum at VMWare recommends Samba connections, at least for VMWare on Linux host for Windows guest.
Otherwise, the VMWare Server virtual machines are completely isolated from their hosts and thus essentially worthless if any kind of data sharing is desired (like here), except via USB drives and/or CD/DVDs.
Not at all, and even if this were the case, it would be listed as a win in my book for just this type of separation.
There are 3 separate types of networking for vmware. You chose the one which isolates the vmware client the most. I'll assume you read the descriptions involved with each option and not bore you with the details here. However the long and short of it is that vmware workstation and ESX have options to set up a share directly with the host. I don't believe vmware server does, however if you have samba properly configured and your firewall is set to allow the SMB/CIFS ports, then you should have no trouble at all emulating this behavior.
As you have it set up with bridging, your host thinks your vmware client is just another system on your network, and will be treated as such for the most part. I suspect your problem lies within your firewall (your error message "Network path not found" is a good clue), and you could test this by disabling iptables temporarily.
Is there another solution for data sharing between Linux and Windows on the same machine (with Linux being the native host OS)?
Sure. apache, webdav, sftp, scp, pick your poison. They all work quite well.
Doesn't WINE do something like this?
No. Where did you get this idea? Wine is a translation layer (a program loader) capable of running Windows applications on Linux. It does not do file sharing between the two unless that's the task of the windows app you're trying to run.
Expecting the impossible, as usual, I suppose....
<Gripe> Well, if you're not going to read the documentation, look at the options within the application you're using, or apply common sense (aka google) then yes, your task may be quite insurmountable. However, if you troubleshoot a bit, look at the actual error messages you're getting you should have it up and running in no time. For that matter, you could probably use the system-config-samba tool or whatever ships with centos to configure samba and get it working. In short: quit your crying, read the documentation and get back to work. </Gripe>
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Jim Perrin Sent: Friday, March 23, 2007 5:36 PM To: CentOS mailing list Subject: Re: [CentOS] RE: Samba config for Windows on VMWare
<Gripe> Well, if you're not going to read the documentation, look at the options within the application you're using, or apply common sense (aka google) then yes, your task may be quite insurmountable. However, if you troubleshoot a bit, look at the actual error messages you're getting you should have it up and running in no time. For that matter, you could probably use the system-config-samba tool or whatever ships with centos to configure samba and get it working. In short: quit your crying, read the documentation and get back to work.
</Gripe>
If I could read that much documentation, absorb it and get it all done in one day, I'd be the envy of every programmer out there, and quite self-satisfied. As it is, I, undoubtedly like you, have to do this sort of thing in between everything else, and, as such, sometimes I skim things here and there and don't always make the right choices. Since I am only two months into this whole new world, I'm actually rather please with how it's going, the impossible being that it isn't already done and working perfectly.
So, please do not read the above as crying, just self-deprecating humor, I'm reading as fast as I can absorb, and a fair amount is still flying right over my head, and all of that in between doing what I need to get my job done and have a reasonably great machine at home with which to practice.
Thank you for pointing this out - a little clarity all around helps us all.
Have a nice weekend - I'll pester you all some more on Monday, hopefully with better questions. :-)
mhr
--- Jim Perrin jperrin@gmail.com wrote:
Otherwise, the VMWare Server virtual machines are
completely isolated
from their hosts and thus essentially worthless if
any kind of data
sharing is desired (like here), except via USB
drives and/or CD/DVDs.
Not at all, and even if this were the case, it would be listed as a win in my book for just this type of separation.
There are 3 separate types of networking for vmware. You chose the one which isolates the vmware client the most. I'll assume you read the descriptions involved with each option and not bore you with the details here. However the long and short of it is that vmware workstation and ESX have options to set up a share directly with the host. I don't believe vmware server does, however if you have samba properly configured and your firewall is set to allow the SMB/CIFS ports, then you should have no trouble at all emulating this behavior.
As you have it set up with bridging, your host thinks your vmware client is just another system on your network, and will be treated as such for the most part. I suspect your problem lies within your firewall (your error message "Network path not found" is a good clue), and you could test this by disabling iptables temporarily.
Is there another solution for data sharing between
Linux and Windows on
the same machine (with Linux being the native host
OS)?
Sure. apache, webdav, sftp, scp, pick your poison. They all work quite well.
Doesn't WINE do something like this?
No. Where did you get this idea? Wine is a translation layer (a program loader) capable of running Windows applications on Linux. It does not do file sharing between the two unless that's the task of the windows app you're trying to run.
Expecting the impossible, as usual, I suppose....
<Gripe> Well, if you're not going to read the documentation, look at the options within the application you're using, or apply common sense (aka google) then yes, your task may be quite insurmountable. However, if you troubleshoot a bit, look at the actual error messages you're getting you should have it up and running in no time. For that matter, you could probably use the system-config-samba tool or whatever ships with centos to configure samba and get it working. In short: quit your crying, read the documentation and get back to work.
</Gripe>
-- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
damn jim why dont you get out the boiling oil too? :-)
Steven
"On the side of the software box, in the 'System Requirements' section, it said 'Requires Windows or better'. So I installed Linux."
On 3/24/07, Steven Vishoot sir_funzone@yahoo.com wrote:
damn jim why dont you get out the boiling oil too? :-)
It had been rumored that my hostility and gruff manner had been declining as of late. Had to show that it's still me :-P
Steven
Mark Hull-Richter wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Jim Perrin Sent: Friday, March 23, 2007 3:23 PM To: CentOS mailing list Subject: Re: [CentOS] Samba config for Windows on VMWare
What networking style did you set up for the vmware client, and how is iptables configured on the host?
Hmm, you're either dazzling me with your brilliance or baffling me....
The vmware client is using a bridged Ethernet adapter (meaning same as the host, I think).
"Bridged" means the guest shares the host's network adapter directly but it looks like a completely different system to everyone else including the host - that is, it needs its own IP address on the same subnet.
Once that is set up, sharing files is exactly the same as with any other machine on the network.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Les Mikesell Sent: Saturday, March 24, 2007 10:21 AM To: CentOS mailing list Subject: Re: [CentOS] Samba config for Windows on VMWare
"Bridged" means the guest shares the host's network adapter directly
but
it looks like a completely different system to everyone else including the host - that is, it needs its own IP address on the same subnet.
Okay, how do I set that up on a single machine (multiple IP addresses)?
On 3/27/07, Mark Hull-Richter mhull-richter@datallegro.com wrote:
Okay, how do I set that up on a single machine (multiple IP addresses)?
You're going to hit a wall with the DSL because it only has one IP. Even after you set up multiple IPs on the machine, the vmware guest won't be able to access the internet until you set up a NAT. So you might as well drop back to using the NAT that vmware can set up for you, and not worry about the requirements for bridging.
Shut down the guest. Log in as root on the host and run
vmware-config.pl
At some point it'll ask you whether you want to keep your current networking configuration. Answer no.
When prompted, select the NAT option rather than bridged.
Then boot up your guest again. You may need to reconfigure networking; the new IP is probably 192.168.8.something, but it should be automatically assigned if the guest uses DHCP.
Once this is working, try your samba config again.
On Fri, 23 Mar 2007 18:18:36 -0400, Mark Hull-Richter wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of John R Pierce Sent: Friday, March 23, 2007 2:28 PM To: CentOS mailing list Subject: Re: [CentOS] Samba config for Windows on VMWare
security=SHARE is for old school win95 networks, with global passwords on each share, I'd avoid that entirely.
use `security=USER`, then read up on smbpasswd. create linux user accounts for each Windows user (same username as they log onto Windows with), then use smbpasswd to set their Samba password to match their Windows login password. Samba can't use their Linux password as SMB networking and Linux use completely different password hashes.
Okay, but (I had to have a but in there), I did not set up the Windows account, and it has a space, and a hyphen, in it (Mark Hull-Richter). Does that work on Linux, or should I go to the trouble of making a new Windows account with a simple name, transferring all the settings and files and so on, etc.?
In Windows 2000 and XP, you would be able to "connect as". In other words, you can specify the username and its password that are known to samba when making a connection. As suggested in the above message, do a smbpasswd -a <username> as root to set up the passwd on the samba server.
Akemi
-
Akemi Yagi -
Bart Schaefer -
Jim Perrin -
John R Pierce -
Les Mikesell -
Mark Hull-Richter -
Scott Silva -
Steven Vishoot