Tag Info

New answers tagged

2

The corrrect way to use SMB name resolution on a Linux machine is to edit (as su) the file /etc/nsswitch.conf and to make sure that the line beginning with hosts contains wins, like this, for instance: hosts: files wins mdns4_minimal [NOTFOUND=return] dns Of course you will be unable to contact any pc not running a SMB server, like for instance ...


1

Connect to your server with SSH and make a tunnel for SMB traffic from your client to your server. Something like: ssh -L 137:127.0.0.1:137 -L 138:127.0.0.1:138 -L 139:127.0.0.1:139 -L 447:127.0.0.1:447 you@your.server.address And then use: smbclient //localhost/Testing -U user This creates a tunnel that forwards traffic from the client computer ports ...


0

Its much easier than what you think (or I am missing something). What I did was on the windows 8.1 PC is: 1.) Control Panel -> Administrative Tools -> Local Security Policy. 2.) Enable - Microsoft Network Client: send unencrypted password to third party SMB servers. 3.) When asked for credentials in user name type: servername\userame.Do not just type the ...


1

You may want to try out: http://mega.co.nz - it allows syncing of 50GB on the free tier, allows sharing links and guest users and things of that nature. It seems like it would fit your needs. I have used this service. It syncs folders/structures across all shares, is not buggy like BitTorrent Sync, and has the benefit of being both Free and, depending on ...


0

While I realize this question has not drawn a great deal of attention, I thought I would post the answer for reference. NET RPC VAMPIRE is not intended to work in the manner I was attempting due to security differences between the two SAMBA versions.


0

The best way is probably to set up the new server, then schedule a maintenance window for turning off normal users' access to the old server. During the maintenance window, use a file copying tool to copy everything you want to keep from the old server to the new one. Once the copying process completes, optionally do a verify step (something like a recursive ...


0

The servers will mange RAID themselves. Just move the data however you want. CAUTION: Ensure the path length of the new server is equal to or less than the file path of the originating server. Users always create directory structures that reach the path length limit, so moving them to a location with even a single character more in the path can cause issues. ...


0

Check out the setup guide at http://thepullen.net/wp/2013/03/using-winbind-to-resolve-active-directory-accounts-in-debian/. Also make sure libnss-winbind is installed. You can test winbind itself with 'wbinfo -u' (should return a huge list of all your domain users). the command 'id xxxx' will try to find info about just user xxx using the ...


0

It makes no difference that it is a raid 5 for these purposes. The raid 5 is to treat multiple drives as if they are only one drive. The software won't care. I don't know about clonezilla. I have done this with Ghost over the network. If clonezilla has an option to copy one computer to another over the network, this would be ideal. The only issue might ...


0

A RAID is operating-system and software transparent since it happens on a firmware / driver level. As far as any software is concerned, a RAID is just one drive. You should be able to just back up the partitions with a standard backup utility (like clonezilla) and throw them up on the new server as-is.


0

got the answer from the wireshark forum: In SMB the FID is send back to the client in the response. Wireshark will show the FID also on the request as it has learned the FID in the response. You can see that the FID is not in the packet, but supplied by wireshark by the square brackets around the FID. So in frame 292, the FID is known, as it is supplied by ...


0

according to your error message, there may not be a group "Domain Users" on your system, do a $ grep "Domain Users" /etc/group possibly you need to do: # addgroup "Domain Users" (as root)


1

Apparently there was a Windows Update in the queue that did something about this. After a restart, this problem disappeared entirely. Update: Oddly, after the May 12 Windows Update and another restart, this problem came back again as before.


0

The SoC device used on the Pi does not have builtin support for ethernet so the ethernet functionality on the Pi is provided by a USB-ethernet chip, sharing the same USB bus as any other USB peripheral you might have connected to it (including any USB flash drives). This is probably the main reason why you see abysmal performance. Solution? Sadly there is ...


0

Based on the details provided in the question, here are some factors that could affect the local transfer rate: The resources on the Raspberry Pi The read speed of the hard drive connected via USB (read speed should typically be high but not sure if drive is faulty) The USB drivers on the Raspberry Pi The USB connecter/external case that connects the hard ...


0

I fixed this issue by changing the Domain/Workgroup name to from WORKGROUP to MSHOME and this fixed my network browsing issues with Linux Mint 17.1 (MATE x64).



Top 50 recent answers are included