Connect Debian stretch with Windows 7

michaelk · 03-29-2019, 07:44 AM

Quote:

It's Linux on a Lenovo tower and Windows 7 on the HP laptop, sorry for not being very clear...

I confused myself.

ssh will not help much unless you install a ssh server on the laptop. Is Windows file sharing setup and working? You should be able to access Windows shares without needing samba server and just use the debian file browser. smbclient would also be a good tool to install.

A script to start up a DHCP server on the debian box would be helpful when directly connecting the laptop because it would simplify find it if the display goes dead.

thomasbb · 03-29-2019, 07:57 AM

Quote:

Originally Posted by michaelk

ssh will not help much unless you install a ssh server on the laptop.

It was to check the link

Quote:

Originally Posted by michaelk

Is Windows file sharing setup and working? You should be able to access Windows shares without needing samba server and just use the debian file browser.

Seriously ?!? Like this ?

Quote:

Originally Posted by michaelk

smbclient would also be a good tool to install.

Ok

Quote:

Originally Posted by michaelk

A script to start up a DHCP server on the debian box would be helpful when directly connecting the laptop because it would simplify find it if the display goes dead.

Following these instructions ?

michaelk · 03-29-2019, 08:17 AM

Yes simple file sharing, Homegroups are not compatible with samba. The file browser has a built in samba client.

You only want to start the DHCP server if the laptop is directly connected to make it easier to find it.

thomasbb · 03-29-2019, 05:31 PM

Quote:

Originally Posted by michaelk

Yes simple file sharing, Homegroups are not compatible with samba. The file browser has a built in samba client.

Yet, they don't see each other...

Quote:

Originally Posted by michaelk

You only want to start the DHCP server if the laptop is directly connected to make it easier to find it.

Here is the /etc/network/interfaces :

Code:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug enp0s25
iface enp0s25:1 inet dhcp

iface enp0s25:2 inet static
      address	169.254.28.75	
      netmask	255.255.0.0
      gateway 	169.254.28.74

Maybe it needs to remove the static gateway ?

Here is the /etc/resolv.conf

Code:

nameserver 10.188.0.1

michaelk · 03-29-2019, 06:08 PM

I assume that your wireless is connected which is why /etc/resolv.conf contains a 10.188.0.1 address. I assume that your debian system is actually using Network-Manager which is managing the network interfaces versus the interfaces configuration file. Does the output of the ip command show the same addresses?

APIPA or link-local addresses i.e 169.254.x.x if enabled are automatically assigned if the client can not communicate with a DHCP server. Using APIPA might work although you need to be able to find the laptop by using the nmap command as illustrated in a previous post. Its been awhile since I have played with using link-local address. It is possible that you could unknowingly assign the same address laptop which leads to an address conflict.

I assume that Network-Manager is running and you can configure a link-local address in the applet which might be ok since this is a what if scenario anyway. As you can tell there are many ways to accomplish the same thing.

thomasbb · 03-30-2019, 03:01 AM

Quote:

Originally Posted by michaelk

As you can tell there are many ways to accomplish the same thing.

The simplest is to install another Linux on the laptop and run a ssh server.