General :: Connect Thin Client To SAMBA PDC Server?
Dec 2, 2009
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 would like have my client computer be able to boot off of a cd right into a terminal server connection. Not click here, then there, enable wireless....so on.. Just boot into a terminal server connection screen.
i want to share the Internet connection to thin client from my Ubuntu server,Internet is accessible to my Ubuntu server but i am unable to boot from thin client to server,i configured DHCP but of no use.can any plz send me the detailed steps to configure thin clients in my network
When I try to connect to the share from my XP machine, I get a "network path cannot be found" error message.
Below is the entry in /var/log/samba/samba.log
[2008/11/19 11:57:51, 0] smbd/service.c:make_connection_snum(1003) '/server2/test' does not exist or permission denied when connecting to [server2] Error was Permission denied
Here is my smb.conf file:
[global] # Server name server string = Intranet Server (Primary)
# These are the default password settings. ; encrypt passwords = yes ; smb passwd file = /etc/samba/smbpasswd
# Define NT domain/workgroup name. workgroup = intranet
# Security mode. (See SAMBA documentation for details.) ; security = user
# Restrict conections to specific IP addresses. hosts allow = all
# The %m variable sets a separate log file for each # connecting machine. # log file = /var/log/samba-log.%m # Keep it basic - one file! log file = /var/log/samba/samba.log
# The number of minutes inactivity before a connection is # disconnected. (This disconnection should be transparent to most # clients, which an have auto-reconnect feature. Removing inactive # connections is to preserve the server's resources.) deadtime = 10
# These socket options are suggested in the default smb.conf file. # Who am I to disagree? socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
# Define both Ethernet interfaces. (Otherwise, I suspect only one # will be configured??) interfaces = eth0 eth1 username map = /etc/samba/smbusers ; guest ok = no ; guest account = nobody
I'm trying to set up a VPN connection between our CentOS 5.3 server at work and my bosses XP computer at home. At this point, we are kinda locked into Quickbooks. I'm testing the connection from my XP boot at home to see if it works. I can log into our servicemanuals easily enough from XP at home however, the windows takes forever to update. I have the Samba server only listening on port 445 because is seems to work more efficiently at work. I connect to the Samba shares via linux from home and everything works well but, when I try to do anything with the shares from Windows client at home, it's very slow!
I'm thinking that it must have something either to do with the Windows OpenVPN client or the client.conf file. Is there anything I should look at in the .conf file for answers?
I am trying to install and configure LTSP on a server for a HP thin client to boot off. The version of Ubuntu that I am using is 11.04 x86 and it is a fresh install on a dual core system with 2GB RAM. I followed a guide which comprised of these commands.
sudo apt-get install ltsp-server-standalone openssh-server sudo ltsp-build-client or if your on a 64-bit system with 32-bit machines do sudo ltsp-build-client arch i386 for editing the servers IP values use /etc/ltsp/dhcpd.conf after that you need to restart DHCP server sudo /etc/init.d/dhcp3-server restart and update sshkeys -sudo ltsp-update-sshkeys and if you updated dhcpd.conf then you need to update you image also by typing in terminal ltsp-update-image
Everything seemed to install as it should but when I try to boot from the thin client it just times out and says no DHCP or proxy invites received. I turned DHCP off on the router and even tried another router, but I still get nothing. I am at a bit of a loose end and I hope someone on here can point me in the right direction of where I am going wrong.
After switching over to linux on my desktop PC (ubuntu) I would like te learn more about linux.I'm trying to get an ELO touchscreen working on an IBM thin client. At the moment I managed to boot it from a CF card.(normally it boots kernel.2200 from a host PC but to avoid interference with the operating system, a flight simulator, I want to try it first with the system booted from a flash card) I tried to install the 32 bit Linux driver from the ELO-website but did not succeed.I was following the manual.I managed to extract the files and copied them to the right directory but when I type in "make" the command is not recognised. I don't know if it would ever work, but when I tried "make" on my Ubuntu machine I get error #2?! What does that mean.
I'm attempting to take Ubuntu 10 down to an image as small as possible to support Citrix Receiver. We currently log them into a browser interface using Firefox where they authenticate against a Citrix DDC and then launch the plug-in. I'm wondering if there is a simple way to determine what services I can shutoff to limit the footprint of the OS. Some of the machines have only 256MB of RAM. They run the plug-in just fine, but there's a lot background activity affecting the machines...
We are using thin client systems in our work environment. There is a central ubuntu server and by using thin clients, we are connecting to our homes. The problem is when I try to install an application, it reported me that I had 200 mb of disk space. But when i try to look from console, I see that /home folder has over 250 gb s of disk space. Even when I try to look from baobab, Disk Usage Analyzer in Ubuntu, i see that my home file system is full.
So what's the reason that I am receiving different kinds of disk space report from different sources? Our system admin here told me that some applications foolishly try to see the physical devices on the thin client and got confused as a result. Is this true?
I just finished setting up a new computer lab at my kids school, using LTSP and 22 think clients connecting to Ubuntu.Everything is going beautifully, and I'm using static IPs and autologin so that when each computer is turned on it logs itself in with no userintervention. The problem is, when users go to the top right system menu and select "Shut Down", they are brought out to the login screen for a second and then immediately logged back in automatically to the Desktop. How should I be shutting down the thin clients?he only way to do it at the moment is to have everyone hold the power button down until the CPU shuts off, but it feels sloppy and unhealthy.
I have an old HP T5700 thin client. I have replaced the FLASH memory with an 2.5" hard drive and have installed a minimal version of Ubuntu Lucid on it. I would like to get the audio to work - specifically the microphone. sudo aplay -l gives:
is there anyone knows how to setup and configure thin client in edubuntu 10.04?. From the beginning installation until thin client work.we have 2 set of computers. 1 computer installed edubuntu 10.04 and installed LTSP (Linux Terminal Server Project) in the OS without NIC Card. And the other computers has only NIC card.. We setup it in the bios as a "First Boot" Network Card. We connect 2 computers using "pair-to-pair connection". There and after, we restart the 2 computers. "Nothings Happened".
I have been working/implementing LTSP based thin clients now using Ubuntu 10.04 LTS 32bit server. I intend to change the default purple Ubuntu splash. I have already removed the "quiet splash" parameters in the pxeconfig file. And it works, giving me a text boot. But what i needed was a replacement for the splash.
I am trying (desperately) to setup freeNX so that I can access my Mandriva box from my Macbook over my network. I have great need to be able to do this. Here's the necessary info for you: Mandriva PC: running Mandriva 2010.0 with freeNX installed from the Mandriva repos Macbook: running OS 10.4 with the Nomachine NX Client installed Now, I have followed the setup from the Mandriva wiki as well as the freenx wiki to no avail. I simply cannot connect the Macbook's NX client to the server. I get an authentication failed message. However, I can ssh from the Macbook to the server just fine (that's how I'm getting most of this work done).
Environment: Ubuntu 9.04 Server/Thin Client. I tried to use KTouch in a classroom with 20 students working at thin client workstations. I thought KTouch was supposed to keep track of the students' typing statistics, what lessons they completed, etc. However, the students get no statistics or any record of what they have done.
Where can I find information on how KTouch is supposed to record/store this information?
I have a server at home running as a file server and DHCP connected to a switch with a wireless AP in there as-well. with this setup I can access the files and do some configurations via SSH on the actual server anytime I'm able to get the wireless signal, now lately I felt the need to be able to do the same but this time over the internet. I've read somewhere already that I'm gonna need a router with port forwarding and NAT, then know the IP address of the server but my problem is once you start talking about routers then you need broadband connection which is something I don't have. Getting a router is not much of a problem but without ADSL like connection I guess its useless, what do I need to do?
I have a CentOS + Samba server and Windows XP client machines. Users, passwords and permissions are entered on the server machine.users and passwords ( same as on the server ) are entered in the XP client machine.When attempting to access a public file on the server using a XP client machine and the IP address of my server, I am asked a user name and password and none of the already entered seem to work. I cannot access the server file (prompted again and again to enter user name and password). What did i miss
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.
Code: # Samba config file created using SWAT # from UNKNOWN (Q@) # Date: 2010/12/08 12:59:41
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.
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.
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.
how to make a new Ubuntu 9.10 box use our LDAP/Samba server for user authentication. Our Red Hat and Windows machines all use it just fine. I've been trying to use the auth-client-config and libnss-ldap packages for this purpose, but I must be missing something. I'm pretty green with LDAP, so this is my first time diving in... Is there a good How-To or step-by-step read on this? All of my searches lead me to setting up Ubuntu as the server, and that isn't what I want. I've also tried the steps listed in [URL] for the LDAP Authentication section.