Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: Networking 101

  1. #1

    Default Networking 101

    I am having trouble making an Opensuse Server and a Windows 10 Machine communicate. I have an old server I was using for use as a PC but got frustrated because when I increased Ram it started acting foolish so I bought a prebuilt. A couple weeks ago I decided to dust off the server and put Opensuse on it and use it as a Server mainly for file storage and share right now. I have tried following various online guides to get the two machines to communicate but nothing I have tried has worked at all.

    Running Win 10 with latest updates along with a couple distros of Ubuntu on main machine. Latest version of Opensuse on Server. Both are hardwired into Gateway, do not currently have internet service to cut down on some bills so we use the hotspots on our phones

    I have never done any home networking because I never needed stuff to communicate in a manner that they needed to share files. Please be gentle and talk to me like a child so I understand what I am doing

    Reasons for file sharing. I have a USB 3 add on card in server and all my externals are USB 3 and eventually when I get my radio show and band moving along I will be using the server to handle online music and stuff

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,768

    Default Re: Networking 101

    Hallo and welcome.

    That is a lot of story telling, but not much factual information.

    Is your NIC functioning and has is a IP address?
    Code:
    ip addr
    Can you reach that Windows system at all?
    Code:
    ping -c1 <IP address of the windows system>
    Without such basics, you can not hope to realy exchange data over the LAN.
    Henk van Velden

  3. #3
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,849
    Blog Entries
    2

    Default Re: Networking 101

    Need info about your machine, run the following command in a windowed console (like Konsole if you installed KDE, but can be any app your machine calls a "Terminal")
    Code:
    cat /etc/os-release
    Also,
    If you think you made more progress following any guide, although you were unsuccessful, post the link to that guide. It'll probably be easier to help you with a guide(If we agree it's a worthwhile instruction) than to start from scratch.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  4. #4

    Default Re: Networking 101

    Quote Originally Posted by tsu2 View Post
    Need info about your machine, run the following command in a windowed console (like Konsole if you installed KDE, but can be any app your machine calls a "Terminal")
    Code:
    cat /etc/os-release
    Also,
    If you think you made more progress following any guide, although you were unsuccessful, post the link to that guide. It'll probably be easier to help you with a guide(If we agree it's a worthwhile instruction) than to start from scratch.

    TSU
    here is what the info on my machine
    Name="openSUSE Leap"
    Version="15.1 "
    ID= "opensuse leap"
    ID_Like="suse opensuse"
    Version_ID="15.1"
    Pretty_Name="openSuse Leap 15.1"
    ANSI_Color="0;32"
    CPE_Name="cpe:/opensuse:leap:15.1"

    The two guides I tried were https://www.tweakhound.com/linux/samba/page_1.htm and https://forums.opensuse.org/showthread.php/528500-Setting-up-openSUSE-amp-Win10-file-sharing

  5. #5

    Default Re: Networking 101

    Quote Originally Posted by hcvv View Post
    Hallo and welcome.

    That is a lot of story telling, but not much factual information.

    Is your NIC functioning and has is a IP address?
    Code:
    ip addr
    Can you reach that Windows system at all?
    Code:
    ping -c1 <IP address of the windows system>
    Without such basics, you can not hope to realy exchange data over the LAN.
    Hi and thank you. Sorry I was trying to explain what I was doing. When I tried pinging my windows pc I got bash:syntax error near unexpected token 'newline'

  6. #6
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,768

    Default Re: Networking 101

    Quote Originally Posted by MashedPotatoes999 View Post
    Hi and thank you. Sorry I was trying to explain what I was doing. When I tried pinging my windows pc I got bash:syntax error near unexpected token 'newline'
    First, please do not use fancy colours, it makes things difficult to read and has no added value.

    Then, please show what you do and get:
    There is an important, but not easy to find feature on the forums.

    Please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.

    An example is here: Using CODE tags Around your paste.

    Your ip addr output is missing complete from your answer.
    And when you get a syntax error in bash, you can be sure that that ping did not run at all, thus the ping test is still not done. But again we can not help when we do not see what you did and got.
    Henk van Velden

  7. #7
    Join Date
    Oct 2008
    Location
    Glasgow, Scotland
    Posts
    1,230

    Default Re: Networking 101

    Quote Originally Posted by MashedPotatoes999 View Post
    Hi and thank you. Sorry I was trying to explain what I was doing. When I tried pinging my windows pc I got bash:syntax error near unexpected token 'newline'
    You seem to have misunderstood or mistyped. This is an example of what was expected:
    Code:
    rayh@yoga3:~> ip address
    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
        inet6 ::1/128 scope host 
           valid_lft forever preferred_lft forever
    2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
        link/ether b0:10:41:f3:87:81 brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.76/24 brd 192.168.1.255 scope global wlan0
           valid_lft forever preferred_lft forever
        inet6 fe80::b210:41ff:fef3:8781/64 scope link 
           valid_lft forever preferred_lft forever
    3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
        link/ether 00:0e:c6:cd:12:5b brd ff:ff:ff:ff:ff:ff
    
    rayh@yoga3:~> ping -c2 192.168.1.117
    PING 192.168.1.117 (192.168.1.117) 56(84) bytes of data.
    64 bytes from 192.168.1.117: icmp_seq=1 ttl=64 time=1.61 ms
    64 bytes from 192.168.1.117: icmp_seq=2 ttl=64 time=1.13 ms
    
    --- 192.168.1.117 ping statistics ---
    2 packets transmitted, 2 received, 0% packet loss, time 1001ms
    rtt min/avg/max/mdev = 1.133/1.374/1.616/0.244 ms
    rayh@yoga3:~>
    Is the Leap-15.1 server connected to the Internet? Can you access this forum from it? If possible can you copy and paste your terminal commands and their output into your forum posts (and include them inside CODE tags)?
    --
    slàinte mhath,
    rayH

    ~ knowing the right answer is easier than knowing the right question.

  8. #8

    Default Re: Networking 101

    Quote Originally Posted by hcvv View Post
    First, please do not use fancy colours, it makes things difficult to read and has no added value.

    Then, please show what you do and get:
    There is an important, but not easy to find feature on the forums.

    Please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.

    An example is here: Using CODE tags Around your paste.

    Your ip addr output is missing complete from your answer.
    And when you get a syntax error in bash, you can be sure that that ping did not run at all, thus the ping test is still not done. But again we can not help when we do not see what you did and got.
    I don't know why it changed the colour of the text. I must have hit something by accident. I will us the CODE tags next time. But I took a picture with my phone and then typed it out because I am using my main for internet connection with my hotspot

  9. #9

    Default Re: Networking 101

    Quote Originally Posted by eng-int View Post
    You seem to have misunderstood or mistyped. This is an example of what was expected:
    Code:
    rayh@yoga3:~> ip address
    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
        inet6 ::1/128 scope host 
           valid_lft forever preferred_lft forever
    2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
        link/ether b0:10:41:f3:87:81 brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.76/24 brd 192.168.1.255 scope global wlan0
           valid_lft forever preferred_lft forever
        inet6 fe80::b210:41ff:fef3:8781/64 scope link 
           valid_lft forever preferred_lft forever
    3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
        link/ether 00:0e:c6:cd:12:5b brd ff:ff:ff:ff:ff:ff
    
    rayh@yoga3:~> ping -c2 192.168.1.117
    PING 192.168.1.117 (192.168.1.117) 56(84) bytes of data.
    64 bytes from 192.168.1.117: icmp_seq=1 ttl=64 time=1.61 ms
    64 bytes from 192.168.1.117: icmp_seq=2 ttl=64 time=1.13 ms
    
    --- 192.168.1.117 ping statistics ---
    2 packets transmitted, 2 received, 0% packet loss, time 1001ms
    rtt min/avg/max/mdev = 1.133/1.374/1.616/0.244 ms
    rayh@yoga3:~>
    Is the Leap-15.1 server connected to the Internet? Can you access this forum from it? If possible can you copy and paste your terminal commands and their output into your forum posts (and include them inside CODE tags)?
    It is not currently connected to the internet because it is not playing well with my wireless adaptor

  10. #10
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,308
    Blog Entries
    14

    Default Re: Networking 101

    Quote Originally Posted by MashedPotatoes999 View Post
    It is not currently connected to the internet because it is not playing well with my wireless adaptor
    Just saying: Don't rely on wireless connections for a server. Do you have an ethernet cable? Can you connect your machine to your router with a cable?
    And mind: most modern operating systems 'need' an internet connection.
    Re. the wireless: can you take photos from the screen, put them somewhere on the web and share the URL here?
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •