Software :: Samba Client - Cannot Resolve Name Error
Jul 6, 2010
I am trying to send a message to a windows machine using smbclient have few questions
1. Do I need to have samba server running on the senders side for this to work smbclient -M -L sam (since there was some error popping up when I try to execute this with out samba service running part of the error is tdb(/var/cache/samba/unexpected.tdb):
rec_read bad magic 0x43414341 at offset=4652)
2. After I started the samba service I am getting fallowing message and error
I tried both name smbclient -M -L sam and the IP smbclient -M -I 192.168.11.12
added interface ip=192.168.11.20 bcast=192.168.11.255 nmask=255.255.255.0
Cannot resolve name -L#0x3
I installed SLES 10.2 with SAMBA 3.5.5.43 to retire our old Microsoft Windows 2000 Server and save some money. All was fine until last week when our chief asked to me to set password expiration for all clients. This morning, all users cannot logon because, when they logon, windows asks to change password and then it gives error error "Access Denied".
I am trying to setup openafs-client but I am having a problem when starting it. I am using a fresh install of OpenSUSE 11.3 and I installed the openafs, openafs-client, krb5 and kernel (default) packages from the filesystems respository of 11.3. When I start the client, either by hand or with the runlevel settings from yast I get the following errors code...
I have been trouble shoot for whole day. I still cant figure out where is my error on write access deny for backup directory on windows SP3. It can read data on explore users by \10.1.23.124ackup code...
I got my server set up with 10.04, and with everything installed: DHCP, SSH, Samba, VBox, etc.
DHCP, SSH work fine, but I am having problems where I cannot ping the hostname of the machine.
It worked for a few minutes after I got everything installed and now it's not letting me connect via hostname. I can connect fine if I use the IP address. I cannot ping the machine by hostname unless I add it's IP address to the hosts file.
After upgrading my ubuntu server from 9.04 to 10.04, the window computers couldn't resolve samba shared names anymore, the error code displayed by Windows was 0x80070035.
I was using the ubuntu server as a samba server, using 'share' as the security authentication method, it has been working very well under previous ubuntu versions but, after upgrading to 10.04, the windows computers can't access the server shares anymore; the linux computers don't have any problems (I can access the shares from linux).
As a workaround, I've added the name of the server in c:windowssystem32driversetchosts; but I'd like to know how to fix the problem without modifying every windows computer.
I would like to be able to mount a share served by my mac os X machine(10.6.1). I have read the Ubuntu community doc on Ubuntu samba clients.It didn't say what to do when using dynamic LAN I.Ps.I understand the way to go is to use avahi on the client side(Ubuntu) and Bonjour on the server side(mac os 10.6.1).I can't find anything about how this is done.What do i need to do to set up the client side(Ubuntu) to use avahi with SAMBA?.Because in the Ubuntu community doc it just referenced /etc/hosts, which is for static I.Ps.So i'm assuming that SAMBA on Ubuntu doesn't use avahi by default.All i need to know is how to set up the client side of SAMBA on Ubuntu when i'm using dynamic LAN I.Ps.
I have a very nice SUSE 11.2 Samba PDC that runs well with Windows XP clients. I am using NETBIOS for name resolution since I dont want to put in a DNS server because my router already has one, Im pretty sure it would make things more complicated. I enabled wins support in smb.conf and made the name resolve order with lmhosts first. lmhosts lists all the ip adresses with their computer names in capitals. I hope thats right. I set up my windows 7 with the reg file from the samba wiki on windows 7 [URL].
That's great now I get the old screen from XP in windows 7 when joining the domain. I gave the machine netbios name MAINPC a smb trust account MAINPC and added the unix user MAINPC$ that should all work. I manage to successfully join it says welcome to domain, afterwards an error appears "changing the dns name of this computer to "" failed" and something bout not finding the domain controller. although I joined. then I resatart and when I try to log on it says "trust relationship failed". How to make it join and logon properly.
So a while back I decided I wanted to get to know Linux a little bit and I figured the most immediately useful thing for me would be a small home server. About this time I discovered plug computers and I eventually bought myself a Guruplug for this purpose - a small, cheap, power-efficient ARM architecture thing running Debian 5.0.6. Since then I've kind of ambled along with the project as and when time permitted (installing, tweaking, scouring manpages and tutorials is fun, but takes a lot of time), and have now finally got a nice big external harddrive formatted as ext3 and hooked up to it. The time seemed right to go for the samba install. I installed from the Debian repository, configured using SWAT and immediately hit problems.
Since the only user is me and the only access to the computer is over SSH, I have few accounts - there's root which I've disabled from access altogether, there's my sudoer account magnus, and there's my new test account magnus-smb. This one is a standard user, and has identical Unix password and samba password (added with smbpasswd). I intend to keep this up with a separate samba-access account - I'm a little paranoid about allowing any kind of access to sudoer accounts and won't even let SSHD accept password based logins.
Setting up samba, I basically tried to make it do as little as I needed to get a local file server going. The only share is homes, and its path goes to my external drive. The drive itself is mounted as rw,noexec,user from fstab.
Now, with all of that set up I'd hoped I'd be able to mount my homes shares and go. This proved not to be the case - if I set encrypted passwords = yes, my Windows 7 clients behave differently. The magnus account connects but can't authenticate - all passwords are rejected. The magnus-smb account is apparently accepted but then receives a "network path not found" error. If I set it to no, both accounts are prevented from even attempting to authenticate, and I get an error message about "this account is not approved for logging on from this station" (translation from Norwegian). I've been searching around but not finding much. I did find one article claiming this was easier after samba 3.3 and discovered that my manpages said samba 3.2. Yesterday I therefore decided to reinstall samba from source, only to find that the current stable release (3.5) also claims to be version 3.2 in it's manpages, so I probably might as well not have bothered. Oh well, at least I've installed something from source now.
My smb.conf:
Code: # Samba config file created using SWAT # from UNKNOWN (Q@) # Date: 2010/12/08 12:59:41
This used to work fine, and i cant figure out what happened...
I rebooted, (after umount -a, then commenting out the connected usb drives from fstab and turning them off...reboot...turn on drives one by one, uncomment from fstab, mount -a...its a bit of a drag rebooting! Quite a few updates happened (openSuse11.2)...
I can still browse all the samba shares directly but I cant follow a symlink anymore ("you do not have permission to view this file") from the same windows client to any of them if they are linked as above.
I'm having a problem when browsing shares on other machines. If I hit alt+f2 and enter "smb://server" I get an error saying: Could not open location 'smb://server/' No application is registered as handling this file If I enter "smb://server/share1" everything works fine. Typing the server name without the share name worked fine in Fedora 8, which is what this machine was running before I did a clean install of Fedora 10.
I'd like to have my Samba client update Windows DNS then join in domain. Computer join in domain but DNS not update. OS: OpenSUSE 11.3 Try after join in domain: net ads dns register -d 3
I have installed winbind, portmap, and samba/smbclient packages on the workstation linux ubuntu , which is intended to be client to samba for /etc/password attached to the server. At boot nothing changed, and the /etc/password is not attached to samba. So my passwords are stil the local of hte client, and not the server. This is my config of the client workstation:
I am practising setting up a small network using UBUNTU as a PDC through SAMBA to service xp clients.
I have sucessfully setup DNS on the Ubuntu server using Bind9 and can nslookup from both the client and the server by FQDN and can also ping ipaddress.
I have setup a basic smb.conf file however when I try to add the xp client to the domain I get an error message saying a domain controller for the domain could not be contacted.
I have disabled the firewalls on both the server and the xp client and still get the same error message when trying to join the domain. I've checked my network settings on the client, its set to use a static IP address and the DNS server and WINS server are set as my Ubuntu Samba PDC address.
I haven't been able to see anything odd in the smb.conf file that might cause this issue. I can connect directly to the shares using the samba network account that I created by going to start run and typing in the unc path.
Not sure what the cause of this issue is, I thought it might be a DNS issue on the client. One odd thing I noticed is that when I do nslookup using just the server name and not the FQDN i get a message in dos saying that the default server cannot be found but says that the server name for the [ipadress] cannot be found. It does list the correct ip.
I'm not sure what is causing the problem of stopping my xp client from joining the Ubuntu Samba PDC. I'm using UBUNTU server 10.04.
I'm trying to install the samba client package by running the following command:sudo apt-get install smbfs. However, it hangs forever and times out on [URL]..Reading package lists. Building dependency tree Reading state information... Done The following extra packages will be installed:
cifs-utils The following NEW packages will be installed: cifs-utils smbfs 0 upgraded, 2 newly installed, 0 to remove and 144 not upgraded. Need to get 41.2 kB of archives. After this operation, 184 kB of additional disk space will be used. Do you want to continue [Y/n]? Y
I have Samba PDC server on CentOS 5..we have 10 thin clients in our network which were working fine previously with the windows Terminal services... Now i have replaced my windows 2003 Domain to Samba Domain Controller.. Is there any why i can connect our thin clients with SAMBA DC in the our environment?
i m working on roaming profile where linux is the server & windows is the client... i m implementing it using samba as pdc my linux version is 2.6.27.5-117.fc10.x86_64 but my samba server is not working windows is not authenticating my domain name following is the copy of my smb.conf file
Quote:
# 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 (perhaps too # many!) most of which are not shown in this example
I'll try not to be too wordy. Want to get my openSUSE 11.2 (fresh install) laptop to see my network shares ...not to be a server or share any files. I've looked at 50 websites and everything seems to be "server" and "share" oriented. Maybe I (newb) am confused by the terminology...
I have a router that provides DHCP. My LAN PC's consist of a Vista laptop, an XP DAW, and a Kubuntu file server. Somehow I got Kubuntu configured properly, all of the Windows machines can access it and vice-versa. The Kubuntu smb.conf does not work on this laptop, and it seems overkill -no shares needed here. And yes, I get DHCP and interweb on the laptop -posted this with it.
All I want is access to my (other) network drives from this (openSUSE 11.2) laptop. Not a server, not to share. This is easy... right? It's driving me nuts Is there a Samba configuration that will let me jump onto networks and surf Windows/Samba shares like any old Windoze box browsing Network Neighborhood? Do I have to be a Samba guru?
I just set up an ubuntu 9.10 server (no desktop environment, command line only) and I'm unable to see my samba share. I followed these instructions. Here are the relevant parts of my smb.conf file: Quote:
workgroup = JASONGROUP # I un-commented this security = user
I'd like to access a samba/SSH server which itself is connected to a VPN Server, therefore acting as a VPN Client. As soon as the VPN Connection is established, samba and ssh connections to this VPN Client get a timeout. But not all of them.
To get a better understanding I made an overview. The first one is a general network overview, without any VPN Connection, the second one with the VPN Connection established.
Network Overview without VPN I can access the server in several ways: *From the router via ssh (router runs ipcop with busybox) *From the laptop via ssh (putty via Windows 7) *From the laptop via samba *From the internet via ssh (port forwarding to the ssh server)
Everything is working as it should.
Now the server that runs ssh and samba service connects to a VPN Server on the Internet, this is also working fine. Now it gets weird. The only samba/SSH connection that is still working is ssh directly from the router to the server. Everything else gets a timeout: *From the laptop via ssh (putty via Windows 7) *From the laptop via samba *From the internet via ssh (port forwarding to the ssh server) Network Overview with VPN active
Why is that? It seems from the little understanding I have of vpn and networking, that incoming packages (like samba request from the laptop) don't get send directly back over eth0 but over the vpn connection. This seems somewhat logic, BUT ssh from the router is still working. Why from the router and not from the laptop? I really can't get my head around it.
Configuration Overview
tldr; One Client acts as VPN Client and samba/SSH Server. As soon as the VPN Connection is established samba/SSH stop working, but only partially.
My network is barely functional. I'm running 2 linux servers connected by openvpn (tun) through routers on both sides. There are Windows clients (98 and XP) on both subnets. One server (ls3) acting as PDC for the domain. The Windows clients use the respective linux boxes as gateways. On the server side (ls3 which is both openvpn server and samba server), all the clients can read/write properly to shares on both sides. The problems are all on the client side. Share connections to the server side disconnect after a few moments.
Browsing on the client side windows machines is fine. I can see shares on the server side. Some server side files open and are readable, writable, other server side files will not open. Some samba logon scripts on the server side can be opened from the client side. Others open after a long wait to a blank file! Permissions on server side files are set to 777 for testing. If a file won't open or reads "blank", that doesn't change no matter how many times you try. A non-readable/writable file overwritten by a readable/writable one can be read and written to!
I can ping successfully from any client on either side to any other client by either ip address or workstation name. Firewalls on both side are set to forward tcp and udp traffic going to port 1194 to the respective gateway linux boxes. Iptables on both linux gateways are down for testing. I tried reversing the openvpn server/client roles with the same result; the same physical side of the network had the problem. On one of the windows 98 clients, I wiped out the networking configuration completely and rebuilt it from scratch. Same result.
One one of the windows xp clients, I tried to rejoin the domain. It went through successfully but the result was the same as above. The network was operating smoothly for several years until the client side dsl modem broke last week. It was replaced with a newer model and at the same time I migrated from a pptp connection to openvpn. How to resolve this, Is this something to do with openvpn? Is this a network hardware problem? Am I missing something in the port forwarding on the routers? My smb.conf files are ancient except I added interface tun0. I have never seen 2 files sitting next to each other in the same directory where one opens and the other doesn't!
I'm running Mandrake 9.2 on the client side and Mandriva 2008 on the server side. I have a Sonicwall firewall on the server side, a Westell 7500 on the client side. I note that during the modem install, the http port was opened to the linux box on the client side and the access log got huge over the weekend and I ran out of disk space until I closed it down and deleted the log. I tried a simple test while viewing /var/log/daemons/errors on the client side. From a windows workstation in the client subnet, I opened a dos window and tried to print a file located on the samba server on the openvpn server machine which I knew NOT to be problematic.
The file printed and there were no errors reported in the log. I repeated the test with a known problematic file. The file would not print. The errors log noted: Authenticate/Decrypt packet error: packet HMAC authentication failed I regenerated the static.key file on the server side and scp'd it to the client side and restarted both openvpn's. I checked for duplicate files named static.key on both sides. Same error.
I have set samba domain. I am able to add win 7 and xp clients. All r working fine. But I have a doubt. If I shutdown the samba pdc server, I should be able to login the client machine with the same profile (which I had, when the samba pdc server was up). Now , if I shutdown the sambapdc, I am able to login the client machine, but new profile is being created. How to avoid this.
How to say to samba that the client machine should load the same profile which was created when the server was up and running. I do not want the client machines to create new a profile when the server is down bcoz in windows domain, when the windows domain is shutdown, the client machines are able to login with the same profile (the profile which was created when the domain was up). I wish to have same thing in samba pdc also.
I finished setup Samba PDC with Openldap backend. I can joint Winxp client to domain but can not change pass by press Ctrl + Alt + Delete and choose Change password button
This is my conf. I used samba3x-3.3.8 openldap 2.3.43 slapd.access.conf
Code: access to attrs=userPassword,shadowLastChange,sambaNTPassword,sambaLMPassword by dn="cn=Manager,dc=microhdesk,dc=net" write by anonymous auth by self write by * none
I am not able to configure nfs mounted disk for shareing samba. i have a server X. which configure samba for windows XP client this is done. now i have export X server samba share disk to mount Y server using nfs. this is mount and ok. but i don't share this disk using Y server samba configure.
