We have a mobile website developed for a conference which should be accessible to users thru smartphone/tablet/laptop when they connect to a wifi router.
Is it possible to setup a xampp server on a local pc connected to the router and assign it a url, so that users can type the url and access the website?
Will the users have to type an ip address or would it be possible to assign a url?
I read in some posts that one way would be to setup a captive portal but we do not have the time & resources to setup a captive portal. Kindly correct me if I am wrong.
Thanks in advance,
Raghav
I feel like this could be possible by building out a DNS server for the lan. And entry for your webserver would then have to be in there. Then, in the router settings, specify the local DNS server as the DNS that gets assigned to other LAN computers via DHCP. Any node that connects to the router and uses DHCP to resolve IP settings should get that DNS server. Then when a client attempts to resolve www.website.com, it will ask the local DNS to resolve it and the request will be translated to the LAN address. I have never done this before but it may be worth a shot.
Related
Create-React-App provides a URL that I can connect through my LAN network like this:
Is there a way to expose the NextJS URL through the LAN network?
The server is accessible on the local network, as long as the network is configured properly (and doesn't have something like client isolation enabled). All you need to do is find out which IP address your network's router is allocating to you. On Windows, this can be done by checking the results of ipconfig. On Linux, you can use ip addr. Then, when you want to access the app from another device, just use the IP found above followed by the port set in next.js.
For example, I have a machine whose network IP address is 192.168.1.2. On that machine, I have a Next app running on port 56381.
ready - started server on 0.0.0.0:56381, url: http://localhost:56381
I can access it on my phone by going to 192.168.1.2:56381.
On my Windows 7 Pro laptop I have have created a VMWare virtual Windows Server 2012 R2 running Active Directory and IIS. I used this walk-through to guide me.
The idea is to setup a development environment for a website that uses AD authentication.
The first issue I have is the IP address of the AD domain controller keeps changing, seems a daily thing.
using the command prompt I use: _ldap._tcp.dc._msdcs.Domain_Name
two days ago: 192.168.174.131
yesterday:192.168.174.134
today:192.168.174.137
As per the walk-through under the section heading 'Configure the server to communicate with the AD domain' I configure the server to communicate with the AD domain by setting the IPv4 DNS IP, however if this keeps changing that is an issue isn't it?
Also in the walk-through, under the section heading 'Add a DNS A record for the web site' it uses the same IP address, so it is an issue here as well.
Afraid I haven't done much networking.
Can someone please tell me why this is happening, if it should be happening and possibly a resolution please.
Have I missed something in the walk-through or has it missed something?
The first issue I have is the IP address of the AD domain controller
keeps changing, seems a daily thing. using the command prompt I use:
_ldap._tcp.dc._msdcs.Domain_Name
two days ago: 192.168.174.131 yesterday:192.168.174.134
today:192.168.174.137
The reason why your AD Domain Controller's IP-Address keeps changing might be because you have not configured a static IP-Address for your DC. For an AD Domain Controller, it should have a static IP-Address, or else the systems joined to this AD domain won't be able to communicate with the DC. It is recommended to have a static IP-Address for your AD DC servers.
The article has not shared the steps for setting up a DC, and I think you've mixed it up by setting up AD DS and IIS on the same server. Usually, as a recommended practice, a server having AD Domain Services role should not install additional roles like IIS. I assume you're using this just for experiment.
As per the walk-through under the section heading 'Configure the
server to communicate with the AD domain' I configure the server to
communicate with the AD domain by setting the IPv4 DNS IP, however if
this keeps changing that is an issue isn't it?
I am assuming you've configured this server an AD DC in itself too, and so you need to assign a static IP for this server.
In the shared image, for the 3rd part where you've configured the DNS, you also need to assign a static IP on the top. In the current image, the default option which you've selected is "Obtain an IP Address automatically". You can assign a static IP like any of the values in the same range (e.g., 192.168.174.131, OR 192.168.174.134, OR 192.168.174.137).
In short, whatever is your AD DC's IP-Address, other systems joined to that domain should use that as a DNS value for their network configuration.
Also in the walk-through, under the section heading 'Add a DNS A
record for the web site' it uses the same IP address, so it is an
issue here as well.
The DNS A record (Address record) is used to point a domain or a subdomain to an IP-Address of the system hosting that domain. You can think it as IP-Address resolution for the URL.
In the article pointed by you, they have done this to help other internal systems resolve your URL into the IP-Address to reach your server which is hosting the website. As AD DC has the DNS role too, you can configure A record in the AD DNS. This setting has to be done on the AD DC server.
Afraid I haven't done much networking.
Can someone please tell me why this is happening, if it should be
happening and possibly a resolution please. Have I missed something in
the walk-through or has it missed something?
This is just an advice from my side it'd be helpful if you go through the basic networking stuff and DNS before proceeding ahead with the article content. It'd be very useful for you if you have a good networking idea which will help you to understand the AD concepts very smoothly.
I hope this answer helps you.
I've been searching the internet the whole day... I cant find my solution.
What I have:
- Xampp server installed en configured
- Working website (local)
- Local ip
- External ip
- Port 80 and 8080 allowed in Firewall
What I want:
- Enter my website and database from any network over my IP address. So, when I am at work, I want to access my website using my (external) IP address.
I am working on a RSS feed in a website and mobile android application, the app is connected (should be) with the website's database. But for this, I need a working IP address.
Can anyone tell me step by step what is have to do? I am not a leek, but not good in English.
Ok, you can access your XAMPP outside of you computer is possible only if you are in same network on which your computer is connected. I mean; consider the local ip of you computer where xampp is installed is 192.168.100.1 then you can access it from any ip like 192.168.100.xyz.
Now if you really want to access it from outside of your network you can set up a VPN or port forwarding.
There is a easy solution is to use ngrok. You can get details here
It is really simple to set up.
i am new for openshift apps, so i make an app in openshift website and i need to point a domain to its web address .
so my domain provider only allowed to set domain based on Website Nameservers . so i want to know is my Website Nameservers i openshift is static, or may be changing in future.
For example my site address is
app-mysite.rhcloud.com
and it's Nameserver is :
ns1.p23.dynect.net with IP 208.78.70.23
.so if i set my domain NS Recorde to ns1.p23.dynect.net it will work .and Nameserver of app-mysite.rhcloud.com will be change in future or no. (Because in openshift site they have said IP address of app-mysite.rhcloud.com maybe change do to server maintenance or ...)
The best way to configure custom domain names with your OpenShift applications is through the use of CNAME certs, see this post for more information https://www.openshift.com/blogs/domain-names-and-ssl-in-the-openshift-web-console. That being said providing the name of your domain provider might be helpful.
Your application IP will inevitably change since your application will unlikely stay on that node. Take a look at the article I mentioned earlier and if you follow those steps your custom domain should persist regardless of your application IP.
I have a mobile webserver, which is connected to internet through GPRS. ISP only provide a private IP, so is not possible to access to it using something like no-ip or dyndns. Is there a way to use a proxy server to access to this mobile webserver?:
Mobile webserver stablish connection with proxy server
a web browser (client) stablish a connection with the proxy server, and redirect the stablished socket directly to mobile webserver
I need to have several of these type of mobile web server (each with a different hostname) connected to a proxy server (ie. its domain is myproxy.com), and provides to a normal user a web site in mobileserverlist.myproxy.com with a list of links, each link will point to ie
http://mobilewebserver1.myproxy.com
http://mobilewebserver2.myproxy.com
http://mobilewebserver3.myproxy.com
here the proxy server will redirect traffic to each mobile web server (all of them in private networks)
ideas?
You mean you have for example a mobilephone as a web server. You can't get a static ip adress and even no dyndns domain. That you can't get dyndns domain is surprising. But you dont really need a proxy. You can easily set up a request script, that direct your users to the location you want.