Issues connecting remotely.

[Mhart08]

first time user and a completed beginner.

I purchased a Raspberry pi 4 and did not have any issues with the initial d/l and installation using a monitor. Once I was up and running I enabled SSH and VNC so I can start doing things remotely.
The issue I am having is I can only connect to the pi remotely after I have logged in on the monitor. If I try and access the pi remotely before I log in on the monitor, Putty times out searching for my IP and if I use CMD it says SSH is not a command. Once again I can only use it remotely when I am logged in using a monitor.
Any input is greatly appreciated.

Here is what I am using.
-Raspberry pi 4
-TightVNC
-Putty
-VNCViewer
-Ethernet connection for internet

[FTrevorGowen]

first time user and a completed beginner.

I purchased a Raspberry pi 4 and did not have any issues with the initial d/l and installation using a monitor. Once I was up and running I enabled SSH and VNC so I can start doing things remotely.
The issue I am having is I can only connect to the pi remotely after I have logged in on the monitor. If I try and access the pi remotely before I log in on the monitor, Putty times out searching for my IP and if I use CMD it says SSH is not a command. Once again I can only use it remotely when I am logged in using a monitor.
Any input is greatly appreciated.

Here is what I am using.
-Raspberry pi 4
-TightVNC
-Putty
-VNCViewer
-Ethernet connection for internet

1) How is your Pi setup to boot to: ie. desktop or command line? (I prefer the latter & run startx if I want the deskstop ie. am not "headless")
2) Are you auto-logging in? (not necessary)
3) Do you have specific reasons to use TightVNC etc. rather than RealVNC that is supplied within Raspbian etc? (The RealVNC server has a virtual mode that allows you to specify a resolution w/o setting a default within raspi-config. See examples here: https://www.cpmspectrepi.uk/raspberry_p ... uster.html . Note that this approach means that you login via PuTTY first and then start the server)
Trev.

[Mhart08]

It is set up to Boot to desktop.
I do not have auto-log in.
I was going to use RealVNC but someone who has experience in controls recommended TightVNC.
I appreciate all your help and will be using your advice when I get home tonight.

[B.Goode]

It is set up to Boot to desktop.
I do not have auto-log in.
I was going to use RealVNC but someone who has experience in controls recommended TightVNC.
I appreciate all your help and will be using your advice when I get home tonight.

As a Moderator has already pointed out... Raspberry Pi themselves document the use of RealVNC, and bundle it with their Raspbian Buster Operating System. Perhaps they know more about their hardware and Operating System than your other source of advice.

https://www.raspberrypi.org/documentati ... /README.md

[Mhart08]

After trying to diagnose where my problem is coming from, I now do not think it has to do with the VNC i was using. It seems I can only gain access remotely when I am directly connected to my internet router. While connected to the router I can access remotely with Putty and VNC Viewer. When I disconnect from the router (and verify that the WIFI on the Pi is working properly) I no longer can gain access remotely.
All input is greatly appreciated.

[B.Goode]

After trying to diagnose where my problem is coming from, I now do not think it has to do with the VNC i was using. It seems I can only gain access remotely when I am directly connected to my internet router. While connected to the router I can access remotely with Putty and VNC Viewer. When I disconnect from the router (and verify that the WIFI on the Pi is working properly) I no longer can gain access remotely.
All input is greatly appreciated.

How, if at all, is your RPi connected to a network if you have disconnected from your router?

[Mhart08]

Once again I will remind everyone that I am a complete beginner with no experience at this and thought this forum might be a friendly place to get some help. I was under the impression you could connect remotely through WIFI. During YouTube and internet searches that seemed feasible.

[B.Goode]

Once again I will remind everyone that I am a complete beginner with no experience at this and thought this forum might be a friendly place to get some help. I was under the impression you could connect remotely through WIFI. During YouTube and internet searches that seemed feasible.

If you interpret what I thought was an entirely reasonable request for further detail of what you are trying to accomplish as somehow not 'friendly' then I will withdraw from the thread.

[FTrevorGowen]

Once again I will remind everyone that I am a complete beginner with no experience at this and thought this forum might be a friendly place to get some help. I was under the impression you could connect remotely through WIFI. During YouTube and internet searches that seemed feasible.

Unfortunately that impression is somewhat "incorrect" (or, rather incomplete). The default/standard setup for a Pi with built in WiFi is for it to be "looking for" a wireless router to be connected to. AIUI, and it's not something I've attempted myself, a Pi can be set up as a wireless access point (or bridge) with the wired ethernet connected to the main network, eg. a (non-WiFi?) router and the WiFi part acting like the WiFi connection of a wireless router. In that situation (or equivalent) then you may be able to connect remotely directly through the Pi's WiFi.
Trev.

[Mhart08]

I was able to connect remotely using WiFi. After checking out the GUI for my router I noticed it gave the Pi an address for when it was connected, which is the address I was using. It gave a different address for WIFI. Using that address everything is working great.