2 Updated link to point to server instead of client instructions
source | link

Rather than accessing the Pi by its IP, you can configure a hostname, and access it by DNS or NetBIOS (with Samba).

If you don't know how to do this, then you can connect your ethernet cable to start and then configure your Pi to the point you can access it by its hostname. Once you do that, you can disconnect the ethernet cable and never worry about knowing the IP again.

I am assuming you are trying to work within a LAN. If you are asking about accessing your Pi remotely, you would probably want to use a dynamic DNS service with port forwarding on your router and/or configure OpenVPN.

For accessing Linux desktops, similar to Windows's RDP, I would suggest using X2GoX2Go.

Rather than accessing the Pi by its IP, you can configure a hostname, and access it by DNS or NetBIOS (with Samba).

If you don't know how to do this, then you can connect your ethernet cable to start and then configure your Pi to the point you can access it by its hostname. Once you do that, you can disconnect the ethernet cable and never worry about knowing the IP again.

I am assuming you are trying to work within a LAN. If you are asking about accessing your Pi remotely, you would probably want to use a dynamic DNS service with port forwarding on your router and/or configure OpenVPN.

For accessing Linux desktops, similar to Windows's RDP, I would suggest using X2Go.

Rather than accessing the Pi by its IP, you can configure a hostname, and access it by DNS or NetBIOS (with Samba).

If you don't know how to do this, then you can connect your ethernet cable to start and then configure your Pi to the point you can access it by its hostname. Once you do that, you can disconnect the ethernet cable and never worry about knowing the IP again.

I am assuming you are trying to work within a LAN. If you are asking about accessing your Pi remotely, you would probably want to use a dynamic DNS service with port forwarding on your router and/or configure OpenVPN.

For accessing Linux desktops, similar to Windows's RDP, I would suggest using X2Go.

1
source | link

Rather than accessing the Pi by its IP, you can configure a hostname, and access it by DNS or NetBIOS (with Samba).

If you don't know how to do this, then you can connect your ethernet cable to start and then configure your Pi to the point you can access it by its hostname. Once you do that, you can disconnect the ethernet cable and never worry about knowing the IP again.

I am assuming you are trying to work within a LAN. If you are asking about accessing your Pi remotely, you would probably want to use a dynamic DNS service with port forwarding on your router and/or configure OpenVPN.

For accessing Linux desktops, similar to Windows's RDP, I would suggest using X2Go.