Connecting to Ubuntu Server 22.04 (locally installed)

Hi,
Odd, I didn't see any questions like this in the forums, didn't think I was the first (or maybe I missed it?)

I set up an old computer as a server locally on Ubuntu server 22.04 to run Redash (data analytics). So far, thanks to a helpful person at Redash, I have been able to install it (and tests on the server indicated all is installed and working) , but my Solus/Budgie laptop does not connect with it (direct LAN cable no router in between) by adding the local server IP in the URL.

It's a clean Ubuntu server install (fully updated), other than Redash, nothing else on it.

I found the local IP address of each machine and tried both ways:

On the Ubuntu server I tried:
sudo ip address add (ip / subnet dev)
but says "can't find device (and the dev number)

On the Solus side I tried two ways:
1) to connect though the File manager (at the bottom it says 'connect to server) and I tried entering in the local server IP with all the prefixes listed (and without any prefix), none worked
2) set up a new 'Network Connections' - basically tried everything (mostly in IPv4 Settings), 'automatic' (two options), manual (with ip/netmask/gateway filled in) and even 'link-local only' since they are connected directly by LAN cable), none worked

Is there something I missed on the Solus side?

Thanks,
Mike

It's not really like just connecting two Linux computers - since this desktop that has Ubuntu server on it was actually used as a server many years ago, it has LAN output (forget what it's called) that used to go to a wi-fi router, then from there we could hook up 3 - 4 other desktops. I just thought it would be simpler to hook my current Solus laptop to that one LAN output port since it will be the only computer connected to the server.

I supposed I should test by putting the router in between?

Or is this a 'networking' issue so should be I on the Ubuntu forums to get assistance? I have very low networking knowledge.

I completely forgot about Webmin (and now Cockpit)! This should make it much easier setting up my 'network'. I'll install one of these and try again.

Axios yea, it's been so long that I had a server set up that I forgot our set-up (and I only maintained it, I did not set it up). The wi-fi router was before the server, and an Ethernet switch was after it, then of course, the desktops connected to the switch.

So I'll get a switch to solve the issue (more common than the crossover ethernet cable, 5 ports, also maybe will add a Raspberry Pi later).

Thanks, and to @TraceyC for the heads up.

Axios I got a basic ethernet switch (tp-link 5 port, TL-SG105), hooked everything up, but when I enter in the address of the server to access 'Cockpit' (https://server address:9090) Solus still does not see anything. It's not a firewall issue as I allowed per instructions on 'Cockpit' (and, tested with 'sudo ufw disable' on the Ubuntu server).

Physical connections:
1) internet ethernet cable to the server (Ubuntu 22.04.3)
2) ethernet cable from server (special LAN out port) to ethernet switch (since there are just 5 ports in the front, I connected this cable to the first one).
3) ethernet cable from ethernet switch (second port) to desktop with Solus OS
(power for the switch is 'on' green light is on)

Software:
1) when I 'ifconfig' on the Ubuntu server, I get three connections, enp2s0, enp5s0 and lo.
2) when I 'edit connection' on Solus OS to add a connection, I choose 'manual' in IP4 and enter in the address, netmask and gateway from enp2s0 (on the Ubuntu machine it says 'broadcast' instead of gateway, so I assume this is it). If I choose 'Auto DHCP' then the pic of the 'wheel' keeps spinning forever and never connects.
3) up until I had added one connection, for the server all was fine, but when I decided to test adding another connection for enp5so, then Solus would no longer display either connection to choose, but rather 'Auto Ethernet', which then just 'spins' forever also. I tried deleting all the connections and starting over, but the 'Auto Ethernet' keeps appearing. And, when I look at the 'Connection Information' for 'Auto Ethernet' it displays the information for the third connection 'lo'

So now I'm really stuck, I've tried so many possible configurations, none seem to work, any suggestions?
Thanks,
Mike

Axios ok, I tried leaving the gateway blank, no changes (firewall I turned off on both machines a long time ago via command line)

strange, when I ping from my Solus desktop to the server on enp2s0 it pings once (looks like the correct line of information) then changes to 'Host unreachable'
when I ping 'lo' it pings normally many times until stopped.
I can't ping enp5s0 as there is no ip address listed (most likely this is for ivp6? it just has something like a MAC address listed)

when I ping from the server to the Solus desktop it says 'Network is unreachable'

yes, each time I click to retry, the lights on the ethernet switch blink once, and, right next to each ethernet port on the switch is a tiny green indicator light (on).

Axios Who knows, since I am not a system administrator and am only stabbing at a solution, I could be doing a lot of things incorrectly. I would have thought most everything would have been automated for setting up a (super simple/basic) network but apparently not.

Plan B - pay a qualified person to set up my network, at least I will learn what I was doing incorrectly.