Connecting to my Windows 7 network

[carlmart]

Ping done.

Can't see a way to upload the results image here.

What do you need to know?

[LTolledo]

on the terminal window highlight the info you want, then right-click, then select copy

then paste the copied contents to the post, enclosing it in {Code}, (its between {Quote} and {List} in the grey tab above when typing a reply)

[carlmart]

Which is the ping command from the Raspberry?

[LTolledo]

yes please...

if you have the ones from the win pc, please post those as well

[carlmart]

Reply from 192.168.1.4: bytes=32 time=2ms TTL=64
Reply from 192.168.1.4: bytes=32 time<1ms TTL=64
Reply from 192.168.1.4: bytes=32 time<1ms TTL=64
Reply from 192.168.1.4: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms

[carlmart]

Now how I ping from the Raspberry?

[Ernst]

Now how I ping from the Raspberry?

Just like on Windows. But before you do so please pay attention to viewtopic.php?f=28&t=240167#p1466662

Some important questions: what is the IP address of the Windows PC and what is the IP address of the Raspberry Pi ?

[carlmart]

PC final number is 2

Pi final number is 4

But when I tried pinging from Pi, i get an unstopping list of ms numbers

[Ernst]

PC final number is 2

Pi final number is 4

But when I tried pinging from Pi, i get an unstopping list of ms numbers

on the raspberry enter

Code: Select all

man ping

or

Code: Select all

ping --help

to get more information on the use of ping.

To stop ping on the raspberry use ctrl-C

Btw. we do not want to know the "final" number, we want to know the complete IP address currently assigned to the hosts.

[carlmart]

IP PC IPv4: 192.168.1.2

IP Pi: 192.168.1.4

Ping seems OK from Pi too.

[Ernst]

This is what I would have posted if I had the same problem:

My Windows PC has the IP address 192.168.0.5 and is connected with an ethernet cable to a switch.

Code: Select all

C:\Users>ipconfig

Windows IP Configuration

Ethernet adapter LAN GBE:

   Connection-specific DNS Suffix  . : xxxxxxx.de
   IPv4 Address. . . . . . . . . . . : 192.168.0.5
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.254

My Raspberry Pi 3 has the IP address 192.168.0.240 and is connected with an ethernet cable to the same switch.

Code: Select all

[email protected]:~ $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:d1:0c:99 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.240/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever

When I ping the raspberry from the windows PC I see:

Code: Select all

C:\Users>ping -n 3 192.168.0.240

Pinging 192.168.0.240 with 32 bytes of data:
Reply from 192.168.0.240: bytes=32 time=1ms TTL=64
Reply from 192.168.0.240: bytes=32 time<1ms TTL=64
Reply from 192.168.0.240: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.240:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

when I ping the windows pc from the raspberry I see:

Code: Select all

[email protected]:~ $ ping -c 3 192.168.0.5
PING 192.168.0.5 (192.168.0.5) 56(84) bytes of data.
64 bytes from 192.168.0.5: icmp_seq=1 ttl=128 time=0.400 ms
64 bytes from 192.168.0.5: icmp_seq=2 ttl=128 time=0.482 ms
64 bytes from 192.168.0.5: icmp_seq=3 ttl=128 time=0.520 ms

--- 192.168.0.5 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2085ms
rtt min/avg/max/mdev = 0.400/0.467/0.520/0.053 ms
[email protected]:~ $

[Ernst]

IP PC IPv4: 192.168.1.2

IP Pi: 192.168.1.4

Ping seems OK from Pi too.

Connectivity seems to be available. The next step I suggest is that you open a command window on the PC and use the "net" command to see what is available like I did below:

Code: Select all

C:\Users>net
The syntax of this command is:

NET
    [ ACCOUNTS | COMPUTER | CONFIG | CONTINUE | FILE | GROUP | HELP |
      HELPMSG | LOCALGROUP | PAUSE | SESSION | SHARE | START |
      STATISTICS | STOP | TIME | USE | USER | VIEW ]

C:\Users>net view
Server Name            Remark
-------------------------------------------------------------------------------
\\RASPI1               Samba 4.5.16-Debian on raspi1
\\TOWER
The command completed successfully.


C:\Users>net view \\raspi1
Shared resources at \\raspi1

Samba 4.5.16-Debian on raspi1

Share name  Type  Used as  Comment

-------------------------------------------------------------------------------
HDD1        Disk  R:       Pi Drive HDD
LUMIX       Disk           Lumix transfer target
The command completed successfully.

C:\Users>

[hortimech]

OK, from what I have read, you are trying to connect via SMB and it doesn't work, try adding 'ntlm auth = yes' to your smb.conf (it will be in /etc/samba). Restart Samba and see if this cures your problem. If it doesn't, please post your smb.conf, but, before posting, remove all lines that start with a '#' or';'

[carlmart]

OK, installed Samba on my Raspbian. Kodi is already installed on it too.

Found smb.conf Where do I add 'ntlm auth = yes'?

How do I do to copy all that's written in smb.conf and put it here? By opening this forum from Raspbian?

[hortimech]

Don't bother, if you had to install Samba you weren't using it, and I know exactly what is in your new smb.conf

You might as well remove Samba, you obviously do not need it, but I still think NTLMv1 is at the root of your problem, perhaps your Win7 PC is using it instead of NTLMv2

[carlmart]

Wait a minute: if I couldn't connect, why not using samba might be the reason for it?

I just tried to connect again with Kodi and couldn't. Would adding that 'ntlm auth = yes' to smb.conf help?

If what you mean that the reason for my problems is because NTLMv1vanished from my Wndows 7, I do think you are right. Something took away my protocol v1 interface, and I stopped connecting with faithful media players. And got into this hell I can't get through.

That's how this all began My media players stopped seeing my network, and I don't know why, because my Windows 7 was "closed for updates".

Well, in any case, I tried and there's no way I can go back to v1.

So, what can I do? Ping seems to work, but my PC does not communicate with the Pi.

[Ernst]

this is a cause for the confusion in this thread:

Hi,

I can't seem to connect my Raspberry Pi3 +B, booted with LibreELEC/KODI, to my Windows 7 PC, by Ethernet.

Why ? What do you want to do ? Is the Pi a client of the Windows PC ? Please explain.
Is this wired or wireless ethernet ?

I have tried everything, loading my IP address under SMB protocol, and I get "Invalid Argument" error.

The IP is correct, so the problem is not there.

What is everything you tried and why ? What IP of what is placed where under SMB protocol ? Is this on the Pi or on the PC ? Where is this configuration ? Did you consult the documentation ? How do you know that the correct IP is placed in the correct place ?

What might be happening?

I don't know, my crystal ball is in for service at the moment.

[Andyroo]

Wait a minute: if I couldn't connect, why not using samba might be the reason for it?
...

Samba is used on the Pi to share its SD card / USB stick with your PC and not the other way around. I thought you wanted to access files on the PC from the Pi - if so can you please:

Can you run the

Code: Select all

net view

command on the PC and pop the results here please?

Then run

Code: Select all

net view \\<computer name> /ALL

and again post the details here?
You will need to replace <computer name> with the name of your PC e.g. \\SUE-LAPTOP (in the case of my wife machine).

The first will show computers on your network, the second will show how things are shared on your PC.

[carlmart]

C:\Windows\system32>net view
Server Name Remark

---------------------------------------
\\CEM-PC
\\DESKTOP-5BD7BIK
\\DESKTOP-PO0ALHS
\\RASPBERRYPI Samba 4.5.16-Deb

[carlmart]

C:\Windows\system32>net view \\CEM-PC /ALL
Shared resources at \\CEM-PC



Share name Type Used as Comment

----------------------------------------------------------------
ADMIN$ Disk Remote Admin
C$ Disk Default share
DVD Player Disk
DVDVolume Disk
E$ Disk Default share
F$ Disk Default share
Filmes Disk
G$ Disk Default share
H Disk
H$ Disk Default share
HP DeskJet 1110 series Print HP DeskJet 1110 series
I$ Disk Default share
IPC$ IPC Remote IPC
Musica Disk
Musica2 Disk
print$ Disk Printer Drivers
Scans Disk
Share Disk
TMP Disk
TMP#2 Disk
Users Disk
utorrent Disk
The command completed successfully.

[carlmart]

This is to be a solely wired system, never wi-fi. The Pi handles the files kept on the PC.

Files are now on my PC, which is also serving as server.

In about two months there will be another PC, loaded with Linuux and CenterOS, that will be the main server, with about 20-30TB of files.

A Raspberry and an Odroid will manage audio & video files respectively.

[Andyroo]

So the two commands show your network stack is working fine on the PC and you have a pile of shares set up.

Which share do you need the Pi to use?

[carlmart]

So the two commands show your network stack is working fine on the PC and you have a pile of shares set up.

Which share do you need the Pi to use?

Only CEM-PC

[Andyroo]

That’s the name of your PC and not a share.

A share is the name of part of the disk on your PC that the Pi needs to access.

[carlmart]

On the media players and on the Mecool, which is also Kodi with Android, what is shared is the whole PC,

You log into it and it opens ALL that is shared within it.