Weird question needs answer

Hi everybody. Today.something weird confused my mind. It is related to "remote access".
For example; in order to get a web page from a web server, a request is sent across the network to the
web server and once we receive a reply, that web page is displayed by our browser as you know. It is the same
once logged in a forum such as here "in fundamental level".
What i am curious about is that considering the first example, when the web page is transmitted, what is
our location that time? are we still on our computer or now we are inside the web server that was gained access? For the second example, question is the same. Are we controlling that server or only just received the page?

If the answer is "we have taken control of the server that time", it is just like using telnet service and
being connected remotely. Also taking control of that particular device. However, how are you gonna
explain the fact that request and reply on telnet? Skipping steps of connection agreement maybe ARP on
local network, first, telnet request is made then reply comes with the password requirement. The password
configured before is entered.If entered correctly, that the particular device is controlled. But, what about the fact that reply arrived "my computer"? So, i still should be on my computer. Imagine the same thing with accessing
the modem/router on your home network through web interface. You type the default IP address of the interface given on the browser such as 192.168.1.1, then it requires from you console password and the username. Once you typed them correctly, now,you are told that you are inside that device now. How about reply that is coming "my computer"?

Find more posts tagged with

SAVE $250 on Your Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View Boot Camps

Comments

Qord

You are not on the server, you are viewing a web page (in a local browser) that the server sent to you, and your browser translates it into something you can read. You are not controlling anything, you just receive a web page that you requested.

As far as being "inside" your router, you are not. If you are looking at the device through a web gui, you are not inside it. Like above, it is acting as a web server of sorts, serving you the configuration web page for that particular device.

thedrama

Qord wrote: »

You are not on the server, you are viewing a web page (in a local browser) that the server sent to you, and your browser translates it into something you can read. You are not controlling anything, you just receive a web page that you requested.

As far as being "inside" your router, you are not. If you are looking at the device through a web gui, you are not inside it. Like above, it is acting as a web server of sorts, serving you the configuration web page for that particular device.

Thanks for your reply. How about telnetting into a remote device(a router for instance)? Telnet request then reply and that device requires password. (must be set at initial configuration of the device) Once telnet session is established successfully, are we now on that device or is it same with above?

RobertKaucher

Please define what you mean by "being on" a computer.

And you might find this funny:

ban comic sans

ccnxjr

This is where PC's differ from servers.
For many of us, when we log in to our PC we are the administrator, with control over the applications, operating system and hardware.
When you interact with a remote system you really interact with services that system offers.
Those services can be web page services, database services, file sharing/management service, or shell services.
Telnet simply refers to the protocol used for you remotely send shell commands to the server and view output.
You are not physically touching the router/switch/remote device, but you are interacting with the shell service.
(think basic operating systems, kernel vs shell)
This concept of a shell has been warped on personal computers (windows and mac alike) where remote administration was an after thought in it's development.
Like web services and file sharing services, the ssh &|| telnet services need to be running on the server for that to work.
The difference being when ssh& telnet is running you get served up a shell instead of a web page or file.
The nature of what you do with that shell is beyond the scope of ssh or telnet.