You are not logged in.
- Topics: Active | Unanswered
#1 2013-01-26 22:07:27
- wolfdogg
- Member
- From: Portland, OR, USA
- Registered: 2011-05-21
- Posts: 545
windows to linux samba connection error for new user[SOLVED]
Im trying to solve a mapped network drive issue. I am trying to connect the mapped drive from a windows machine to run windows backup which is backing up to an arch linux zfs-fuse array on computer "FALCON" from a Win 7 machine called "REDTAIL". Apparently backup was run for the first time from user wolfdogg, so now it doesnt have administrator privileges to other users files. So i figured i would run the backup as administrator on windows, that too didnt solve the problem. So i figured since the drive i was backing up to was mapped from the wolfdogg user, i would map it from the administrator user therefore i suspect that i would be one step further in getting the admistrator credentials to pass through the backup program "HOPEFULLY".
This is where the problem is coming in, when trying to map the drive from the windows machine to the linux box for user 'administrator'. Note, even the file permissions on the backup files in the zfs-fuse "/backup" directory are listed as wolfdogg.
My Setup---
I have the wolfdogg user working correctly, but now i go to set up an "administrator" user on the linux box to debug the windows backup issue and now i cant connect to the arch samba server with the new 'administrator' credentials.
I have two ways to connect, im using 2 different network adapters, one goes through a router thats only 10/100 accessible via \\FALCON, and im using a "crossover" type connection to the 'newer' onboard nics at 10/100/1000 mbps connections accessible via \\192.168.0.1.
The networks---
10/100 network (the slow one)
server name (netbios) \\falcon or \\192.168.1.10
network 192.168.1.0
255.255.255.0
gateway 192.168.1.253 (router)
10/100/1000 network (the fast one)
server name \\192.168.0.1
network 192.168.0.0
255.255.255.0
(straigt cable)
samba config---
[global]
workgroup = LOCAL
server string = Samba Server
log file = /var/log/samba/%m.log
max log size = 50
unix extensions = No
idmap config * : backend = tdb
hosts allow = 192.168.1.,192.168.2.,192.168.0.,127.
#remove printing (CUPS) errors from error.log, if not using a printer
printing = bsd
printcap name = /dev/null
#lanman fix
#client lanman auth = yes
#client ntlmv2 auth = no
[homes]
comment = User Home Directories
valid users = %S
read only = No
wide links = Yes
[backup]
comment = backup drive
path = /backup
valid users = wolfdogg,administrator
read only = No
create mask = 0765
wide links = Yesother important configs---
# cat /etc/passwd
administrator:x:5005:100::/home/administrator:/bin/bash
# groups administrator
disk wheel storage power sudo users
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: net0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1a:4d:62:d9:bb brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/24 brd 192.168.0.255 scope global net0
inet6 fe80::21a:4dff:fe62:d9bb/64 scope link
valid_lft forever preferred_lft forever
3: internet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:90:27:c1:d8:bf brd ff:ff:ff:ff:ff:ff
inet 192.168.1.10/24 brd 192.168.1.255 scope global internet0
inet6 fe80::290:27ff:fec1:d8bf/64 scope link
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.253 0.0.0.0 UG 0 0 0 internet0
192.168.0.0 * 255.255.255.0 U 0 0 0 net0
# vim /etc/hosts
#
# /etc/hosts: static lookup table for host names
#
#<ip-address> <hostname.domain.org> <hostname>
# #localhost works for apache, and falcon works for samba
127.0.0.1 root.lh localhost falcon
127.0.0.1 localhost.localdomain localhost falcon
::1 localhost.localdomain localhost
#192.168.1.99 redtail redtail
192.168.0.2 redtail redtailWindows Machine (REDTAIL) route--
-Note the persistent route that has the Metric of 1, that was the magical route that i had to add to make the redtail talk to falcon directly
C:\ route print
===========================================================================
Interface List
38...00 40 05 0a b8 94 ......D-Link DFE-530TX+ PCI Adapter #2
12...48 5b 39 ca a9 6e ......Realtek PCIe GBE Family Controller
1...........................Software Loopback Interface 1
20...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #5
13...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
15...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #2
27...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #9
18...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #3
19...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #4
21...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #6
22...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
46...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #22
26...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #8
29...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #10
30...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #11
31...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #12
32...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #13
33...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #14
35...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #15
39...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #17
41...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #19
42...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter #20
43...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.253 192.168.1.99 276
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.0.0 255.255.255.0 On-link 192.168.0.2 266
192.168.0.2 255.255.255.255 On-link 192.168.0.2 266
192.168.0.248 255.255.255.255 On-link 127.0.0.1 51
192.168.0.255 255.255.255.255 On-link 192.168.0.2 266
192.168.1.0 255.255.255.0 On-link 192.168.1.99 276
192.168.1.99 255.255.255.255 On-link 192.168.1.99 276
192.168.1.255 255.255.255.255 On-link 192.168.1.99 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.99 276
224.0.0.0 240.0.0.0 On-link 192.168.0.2 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.99 276
255.255.255.255 255.255.255.255 On-link 192.168.0.2 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.0.248 255.255.255.255 On-link 1
0.0.0.0 0.0.0.0 192.168.1.253 Default
===========================================================================
IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
38 276 fe80::/64 On-link
12 266 fe80::/64 On-link
12 266 fe80::2410:30a1:afb7:ec0f/128
On-link
38 276 fe80::64af:74d9:af7b:4649/128
On-link
1 306 ff00::/8 On-link
38 276 ff00::/8 On-link
12 266 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
C:\Users\wolfdogg>Tests that i have done ---
Im trying to connect windows machine "REDTAIL" to linux machine 'falcon'
When "Mapping a network drive" i tried using UNC naming conventions from what i understand but the problem is i cant use the administrator credentials. I need to be able to use them on the \\192.168.0.1 network, but they are not working on either currently
Connections that work / dont work---
ADDRESS \\falcon\backup \\falcon\homes \\192.168.1.10\homes \\192.168.1.10\backup
users that work:
wolfdogg
\REDTAIL\wolfdogg
\FALCON\wolfdogg
users that dont work:
\REDTAIL\administrator
\\redtail\administrator
redtail\administrator
administrator
\FALCON\administrator
ADDRESS \\192.168.0.1\backup
users that work
REDTAIL\wolfdogg
wolfdogg
users that dont work
\FALCON\wolfdogg
\REDTAIL\wolfdogg
REDTAIL\administrator
administrator
Additional notes ---
I also went to windows 7 network and sharing, Home or Work, and Public, and downgraded the setting "File Sharing Connections" to "enable file sharing for devices that user 40- or 56- bit encryption" from 128 bit, just incase
What do i do? --
is there any other configurations i need to be looking for, or where else i need to network in as administrator user?
Last edited by wolfdogg (2013-01-29 16:16:22)
Offline
#2 2013-01-29 16:16:33
- wolfdogg
- Member
- From: Portland, OR, USA
- Registered: 2011-05-21
- Posts: 545
Offline
#3 2013-03-21 09:10:56
- wolfdogg
- Member
- From: Portland, OR, USA
- Registered: 2011-05-21
- Posts: 545
Re: windows to linux samba connection error for new user[SOLVED]
what i was trying do was very complicated to solve. This is basically a multi pronged network connection between two machines that would seem much easier in theory to set up. There was good reason for the need for this, simply because one connection was for file transport between the two machines using a direct Gbps lan connection which bypassed a 100Mbps router, and the 2nd connection was through the router for purpose of connecting to both the internet, as well as allowing other computers on the network to communicate back and forth.
The problem was primarily the windows machine was confused as to which connection provided internet, vs. which protocol to use the direct connection on.
i basically solved the problem on the windows machine by adding a persistent route to the route table for the direct connection, and added the lowest metric to it in the route, on the windows machine, so that when the ip of the machine is mapped to a drive, or access directly via windows explorer, it would take the adapter using the lowest metric. When a browser was opened, windows automatically sees what adapter has internet connection so it had no problem finding the correct adapter to use for this.
as far as the linux machine, i created two static connections using netcfg, and in the hosts file i madded the netbios name to the direct connection so that when the windows machine is accessed via the netbios name it used the Gbps lan connection. When the internet is accessed in anyway on the linux machine it has no problem using the adapter that has the router set as its gateway without any modifications necessary.
So now i get two connections, when the windows backup runs it backups up to the mapped network drive (a zfs array on the linux box), this is a drive letter mapped to an ip address, when this mapped drive is accessed it channels through the route table using the lowest metric adapter (the Gbps lan adapter) and blows at full speed backing up 1.5 TB in about 1/3 to 1/6 the time it would otherwise take to complete the task, a half day vs. 3+ days in my case for 1.5 TB of data.
whoosh, i can leave the windows machine alone now..... family files are safe before drives have time to burn out.... back to programming... ......
Last edited by wolfdogg (2013-03-21 09:14:16)
Offline