What Is Remote IP Address?
What is remote IP address? It refers to the IP address of the remote computer for remote connection over RDP.
By Ellie 
/ Last Updated November 29, 2022
What is my computer IP address for Remote Desktop?
“I had a computer problem and my friend who’s computer-savvy said he can help you to solve the problem remotely using Remote Desktop. But he needs my computer’s IP address for it. So how what is my computer’s IP address and how can I find it?
-Question from Reddit
What is remote IP address and how to find it?
What is a remote IP address, or what is my computer’s IP address for Remote Desktop Connection?
An IP address is a prerequisite to achieving a remote connection via Windows Remote Desktop. If you don’t know the remote computer’s IP address, you won’t be able to connect remotely. Next, let’s learn two ways to get the computer IP address for Remote Desktop.
Way 1. Find out remote IP address via command line
Step 1. Press Win + R to invoke the Run dialog box. Type in cmd and press OK.
Step 2. Then type “ipconfig” and press Enter. Now you can see a group of IP addresses, of which the IPv4 address is the one you need.
Way 2. Find out remote IP address from Windows Settings
Step 1. Click Start and then click Settings. Find Network & Internet and then click it.
Step 2. On the Network & Internet interface, find Advanced network settings, and click Change adapter options below.
Step 3. In the automatically pop-up Network Connections window, find your network and double-click it.
Step 4. On the General tab, find Details.
Step 5. In the Network Connection Details, find IPv4 Address.
Note: After finding out the IP address of the remote computer, you can start to remotely control it using the IP address.
AnyViewer: Achieve remote connection without remote IP address
You may wonder if there is an easier way to achieve a remote desktop connection without an IP address. The answer is YES! You can use the third-party remote desktop software AnyViewer, which is much easier than Remote Desktop. It doesn’t require an IP address to achieve a remote connection. All you need to do is to sign up for it and then you can easily achieve unattended remote access.
Step 1. Download, install, and launch AnyViewer on both computers. Go to Log in, and then click Sign up. (If you already have signed up on its official website, you can log in directly.)
Step 2. Fill in the signup information.
Step 3. Then you can see you successfully logged in to AnyViewer. Your device will automatically be assigned to the account you’ve logged in to.
Step 4. Log in to the same AnyViewer account on the two devices, then you can achieve a direct connection by clicking One-click control.
Step 5. Then you can see the screen of the remote computer and take complete control of it. There’s also a toolbar in the top-middle of the screen, you can change the resolution and image quality, carry out simple operations, and open the chat box here.
Note: If you upgrade your account to a Professional or Enterprise plan, then you’ll have more rights. You can assign more devices. Also, you can connect to another computer in privacy mode, which means you can black the screen and block the mouse and keyboard of the remote computer.
Conclusion
What is a remote IP address? Now surely you have known it. To find out the IP address, you can use CMD or Windows Settings. To get remote access easier without finding out IP address, it’s recommended to use AnyViewer. It offers you a safe and stable connection with flexible connection methods.
Remote IP адрес – что это такое?
Remote IP address (удаленный IP-адрес) – это адрес, присваиваемый компьютеру или устройству в сети Интернет. Когда вы подключаетесь к Интернету, провайдер дает вашему компьютеру уникальный IP-адрес, который идентифицирует ваше устройство среди множества других устройств в сети.
Remote IP address можно использовать для различных целей. Одним из наиболее популярных случаев использования является определение местоположения пользователя. С помощью IP-адреса можно узнать географическое положение устройства и примерное место, где находится пользователь. Такая информация может быть полезной для различных сервисов, например, при предложении контента на основе местоположения или для целей рекламы.
Еще один пример использования удаленного IP-адреса – это ограничение доступа к контенту или сервисам. С помощью IP-адреса можно контролировать доступ к ресурсам, блокировать или разрешать определенные IP-адреса в зависимости от желаемых настроек. Например, многие сайты блокируют доступ для пользователей из определенных стран или регионов.
Также удаленный IP-адрес может использоваться для безопасности и идентификации. При доступе к защищенным ресурсам, например, банковским сайтам или системам электронной почты, сервисы могут проверять IP-адрес пользователя, чтобы убедиться в его подлинности и разрешить доступ только с определенных IP-адресов или сетей.
Что такое Remote IP Address?
Remote IP Address используется для определения местоположения пользователя и обеспечения безопасности взаимодействия сети. Он позволяет узнать, откуда приходит запрос на доступ к ресурсу. Также Remote IP Address позволяет ограничивать доступ к определенным ресурсам или контенту на основе IP-адреса.
Remote IP Address может быть статическим или динамическим. Статический IP-адрес не меняется и используется постоянно для одного устройства. Динамический IP-адрес назначается устройству на определенный период времени и может меняться при каждом подключении к Интернету.
Для получения Remote IP Address веб-серверы часто используют HTTP заголовок «X-Forwarded-For». Он содержит информацию об IP-адресе клиента, который делает запрос. Возможно, команда REMOTE_ADDR или специальные функции в программировании могут быть использованы для получения Remote IP Address.
Remote IP Address имеет различные применения в Интернете, отслеживая активность пользователей до фильтрации или ограничения доступа к определенной информации или услугам.
Remote IP Address: понятие и определение
Remote IP Address позволяет сетевым устройствам обмениваться данными между собой. Он играет важную роль в передаче информации через интернет, поскольку позволяет идентифицировать отправителя и получателя данных.
Когда вы заходите на веб-страницу или отправляете запрос на сервер, ваш браузер передает веб-серверу ваш Remote IP Address. Это позволяет серверу знать, откуда пришел запрос, и отправить вам ответ.
Remote IP Address состоит из четырех чисел, разделенных точками. Каждое число может быть от 0 до 255. Например, 192.168.0.1. При этом, IP-адресы могут быть разделены на публичные и приватные. Публичные IP-адреса являются уникальными во всему миру и используются для идентификации устройств в интернете. Приватные IP-адреса, с другой стороны, используются в локальных сетях и не могут быть доступными извне.
Remote IP Address может быть использован для различных целей. Например, аналитика веб-сайта может использовать эту информацию для определения местоположения посетителей, чтобы предоставлять контент, адаптированный к конкретной географической локации. Также Remote IP Address может использоваться в безопасности сети для блокировки или ограничения доступа к определенным ресурсам или сервисам для определенных IP-адресов.
Как узнать Remote IP Address?
- С помощью простых онлайн-инструментов. На сегодняшний день множество веб-сайтов предлагают возможность проверить ваш IP-адрес. Просто откройте любой из таких сайтов через браузер на удаленном устройстве и ваш Remote IP Address будет отображен на экране.
- Используя командную строку. Если вы работаете с операционной системой Windows, вы можете открыть командную строку и ввести команду «ipconfig», чтобы узнать ваш IP-адрес. На компьютерах Mac и Linux вам необходимо открыть терминал и ввести команду «ifconfig». В выводе команды будет указан ваш локальный IP-адрес, а также Remote IP Address.
- Через сетевые настройки. В большинстве операционных систем есть возможность просмотреть сетевые настройки, где будет указан ваш IP-адрес и адрес шлюза. Remote IP Address будет иметь другой формат и находиться в разделе, который отвечает за удаленное подключение к сети.
Узнав Remote IP Address, вы сможете использовать его для различных целей, таких как удаленный доступ к компьютеру или настройка сетевых служб.
Apache Module mod_remoteip
This module is used to treat the useragent which initiated the request as the originating useragent as identified by httpd for the purposes of authorization and logging, even where that useragent is behind a load balancer, front end server, or proxy server.
The module overrides the client IP address for the connection with the useragent IP address reported in the request header configured with the RemoteIPHeader directive.
Additionally, this module implements the server side of HAProxy’s PROXY Protocol when using the RemoteIPProxyProtocol directive.
Once replaced as instructed, this overridden useragent IP address is then used for the mod_authz_host Require ip feature, is reported by mod_status , and is recorded by mod_log_config %a and core %a format strings. The underlying client IP of the connection is available in the %
Topics
Directives
- RemoteIPHeader
- RemoteIPInternalProxy
- RemoteIPInternalProxyList
- RemoteIPProxiesHeader
- RemoteIPProxyProtocol
- RemoteIPProxyProtocolExceptions
- RemoteIPTrustedProxy
- RemoteIPTrustedProxyList
Bugfix checklist
See also
- mod_authz_host
- mod_status
- mod_log_config
Remote IP Processing ¶
Apache by default identifies the useragent with the connection’s client_ip value, and the connection remote_host and remote_logname are derived from this value. These fields play a role in authentication, authorization and logging and other purposes by other loadable modules.
mod_remoteip overrides the client IP of the connection with the advertised useragent IP as provided by a proxy or load balancer, for the duration of the request. A load balancer might establish a long lived keepalive connection with the server, and each request will have the correct useragent IP, even though the underlying client IP address of the load balancer remains unchanged.
When multiple, comma delimited useragent IP addresses are listed in the header value, they are processed in Right-to-Left order. Processing halts when a given useragent IP address is not trusted to present the preceding IP address. The header field is updated to this remaining list of unconfirmed IP addresses, or if all IP addresses were trusted, this header is removed from the request altogether.
In overriding the client IP, the module stores the list of intermediate hosts in a remoteip-proxy-ip-list note, which mod_log_config can record using the %
IPv4-over-IPv6 Mapped Addresses
Internal (Private) Addresses
RemoteIPHeader Directive ¶
| Description: | Declare the header field which should be parsed for useragent IP addresses |
|---|---|
| Syntax: | RemoteIPHeader header-field |
| Context: | server config, virtual host |
| Status: | Base |
| Module: | mod_remoteip |
The RemoteIPHeader directive triggers mod_remoteip to treat the value of the specified header-field header as the useragent IP address, or list of intermediate useragent IP addresses, subject to further configuration of the RemoteIPInternalProxy and RemoteIPTrustedProxy directives.
Internal (Load Balancer) Example
Proxy Example
RemoteIPInternalProxy Directive ¶
| Description: | Declare client intranet IP addresses trusted to present the RemoteIPHeader value |
|---|---|
| Syntax: | RemoteIPInternalProxy proxy-ip | proxy-ip/subnet | hostname . |
| Context: | server config, virtual host |
| Status: | Base |
| Module: | mod_remoteip |
The RemoteIPInternalProxy directive adds one or more addresses (or address blocks) to trust as presenting a valid RemoteIPHeader value of the useragent IP. Unlike the RemoteIPTrustedProxy directive, any IP address presented in this header, including private intranet addresses, are trusted when passed from these proxies.
Internal (Load Balancer) Example
RemoteIPInternalProxyList Directive ¶
| Description: | Declare client intranet IP addresses trusted to present the RemoteIPHeader value |
|---|---|
| Syntax: | RemoteIPInternalProxyList filename |
| Context: | server config, virtual host |
| Status: | Base |
| Module: | mod_remoteip |
The RemoteIPInternalProxyList directive specifies a file parsed at startup, and builds a list of addresses (or address blocks) to trust as presenting a valid RemoteIPHeader value of the useragent IP.
The ‘ # ‘ hash character designates a comment line, otherwise each whitespace or newline separated entry is processed identically to the RemoteIPInternalProxy directive.
Internal (Load Balancer) Example
conf/trusted-proxies.lst contents
RemoteIPProxiesHeader Directive ¶
| Description: | Declare the header field which will record all intermediate IP addresses |
|---|---|
| Syntax: | RemoteIPProxiesHeader HeaderFieldName |
| Context: | server config, virtual host |
| Status: | Base |
| Module: | mod_remoteip |
The RemoteIPProxiesHeader directive specifies a header into which mod_remoteip will collect a list of all of the intermediate client IP addresses trusted to resolve the useragent IP of the request. Note that intermediate RemoteIPTrustedProxy addresses are recorded in this header, while any intermediate RemoteIPInternalProxy addresses are discarded.
Example
RemoteIPProxyProtocol Directive ¶
| Description: | Enable or disable PROXY protocol handling |
|---|---|
| Syntax: | RemoteIPProxyProtocol On|Off |
| Context: | server config, virtual host |
| Status: | Base |
| Module: | mod_remoteip |
| Compatibility: | RemoteIPProxyProtocol is only available in httpd 2.4.31 and newer |
The RemoteIPProxyProtocol directive enables or disables the reading and handling of the PROXY protocol connection header. If enabled with the On flag, the upstream client must send the header every time it opens a connection or the connection will be aborted unless it is in the list of disabled hosts provided by the RemoteIPProxyProtocolExceptions directive.
While this directive may be specified in any virtual host, it is important to understand that because the PROXY protocol is connection based and protocol agnostic, the enabling and disabling is actually based on IP address and port. This means that if you have multiple name-based virtual hosts for the same host and port, and you enable it for any one of them, then it is enabled for all of them (with that host and port). It also means that if you attempt to enable the PROXY protocol in one and disable in the other, that won’t work; in such a case, the last one wins and a notice will be logged indicating which setting was being overridden.
RemoteIPProxyProtocolExceptions Directive ¶
| Description: | Disable processing of PROXY header for certain hosts or networks |
|---|---|
| Syntax: | RemoteIPProxyProtocolExceptions host|range [host|range] [host|range] |
| Context: | server config, virtual host |
| Status: | Base |
| Module: | mod_remoteip |
| Compatibility: | RemoteIPProxyProtocolExceptions is only available in httpd 2.4.31 and newer |
The RemoteIPProxyProtocolExceptions directive enables or disables the reading and handling of the PROXY protocol connection header. Sometimes it is desirable to require clients to provide the PROXY header, but permit other clients to connect without it. This directive allows a server administrator to configure a single host or CIDR range of hosts that may do so.
RemoteIPTrustedProxy Directive ¶
| Description: | Restrict client IP addresses trusted to present the RemoteIPHeader value |
|---|---|
| Syntax: | RemoteIPTrustedProxy proxy-ip | proxy-ip/subnet | hostname . |
| Context: | server config, virtual host |
| Status: | Base |
| Module: | mod_remoteip |
The RemoteIPTrustedProxy directive restricts which peer IP addresses (or address blocks) will be trusted to present a valid RemoteIPHeader value of the useragent IP.
Unlike the RemoteIPInternalProxy directive, any intranet or private IP address reported by such proxies, including the 10/8, 172.16/12, 192.168/16, 169.254/16 and 127/8 blocks (or outside of the IPv6 public 2000::/3 block) are not trusted as the useragent IP, and are left in the RemoteIPHeader header’s value.
Trusted (Load Balancer) Example
RemoteIPTrustedProxyList Directive ¶
| Description: | Restrict client IP addresses trusted to present the RemoteIPHeader value |
|---|---|
| Syntax: | RemoteIPTrustedProxyList filename |
| Context: | server config, virtual host |
| Status: | Base |
| Module: | mod_remoteip |
The RemoteIPTrustedProxyList directive specifies a file parsed at startup, and builds a list of addresses (or address blocks) to trust as presenting a valid RemoteIPHeader value of the useragent IP.
The ‘ # ‘ hash character designates a comment line, otherwise each whitespace or newline separated entry is processed identically to the RemoteIPTrustedProxy directive.
Trusted (Load Balancer) Example
conf/trusted-proxies.lst contents
# Identified external proxies;
192.0.2.16/28 #wap phone group of proxies
proxy.isp.example.com #some well known ISP
Comments
Copyright 2023 The Apache Software Foundation.
Licensed under the Apache License, Version 2.0.
What is local IP and remote IP while doing port forwarding?
Public IP of my router is 203.144.12.34 , I want to forward port 3000 of this to the web server.
Can someone help what should I fill in the fields below? I don’t understand what details to put where?
2 Answers 2
The port from/to design ranges of ports, so this should be:
- Local IP : 192.168.1.4
- Local Port from : 3000
- Local Port to : 3000
- Protocol : TCP
- Remote IP : Leave empty (any IP)
- Remote Port from : 3000
- Remote Port to : 3000
Outsiders will connect to your server as 203.144.12.34:3000 .
You may use another value for the remote port. For HTTP port 80 usually used (443 for HTTPS if you have set it up), but this well-known port may be attacked if it’s open, so using another port is safer.
What you need is to set port forwarding on your router (your router IP is 192.168.1.1). You didn’t mention what kind of OS you are running on your router, since there could be a different option. But in general: port forwarding (usually if in the firewall).
What you are showing might be a port range forwarding. That can do the job as well. So:
- Name: service name (this is just for you)
- Local IP: 192.168.1.4
- Local port from: 3000
- Local port to: 3000
- Protocol: Either TCP/UDP or Both (both is useful if you don’t know, but usually it is TCP)
- Remote IP: 203.144.12.34 (if blank does not work)
- Remote port from: 3000
- Remote port to: 3000
Then you call your service as 203.144.12.34:3000
If you have a single port forwarding option, you can forward 203.144.12.34:2222 to your local machine 192.168.1.4:3000