For some reason I want a direct-connected PC (using LAN cable) to access ESXi web client without the need to connect to the main LAN network (10.0.0.0 /24). (see diagram below), I have set up a VMkernal in ESXi with "management" service enabled (VMkernel IP: 192.168.1.100). (see the diagram below)
I can ping the secondary VMkernel IP address 192.168.1.100 from PC 2. However, I cannot go to https://192.168.1.100 via web browser.
Is that ESXi doesn't support the configuration like this?
I hope I can access to ESXi web client (IP 10.0.0.30) from the PC 1 and to the same ESXi web client (IP 192.168.1.100) from the PC 2.
Related
Scenario
I'm using Power Bi Report Server - Developer (15.0.1107.116) which is directly connected to Microsoft SQL Server 2008 Database and Microsoft SQL Server 2019 Database, the Operating System is Microsoft Window Server 2019 with Internet Information Service (IIS). IIS already has /RDWeb web portal on 443 port and PBiRS is also on 443 port, both with legit SSL Certificate. Locally both /RDWeb and /Report are accessible in the local area network. I'm also able to connect to IIS main web page from outside of network.
Issue
I can connect with the Report Server /Report web portal on Local Network but when I try to connect to /Report from outside of the network, I get an error of 404 though the same /Report is accessible from Local Area Network.
Points to Note
Firewall is off of (Domain/Private/Public)
Server is in DMZ
IIS Main Webpage is accessible from outside the network
Only /Report is not accessible from outside network
Please keep in mind that this guide is of HTTP 8080 insecure protocol based.
Before starting, I'm assuming that the Power Bi Report Server service running properly, the database is connected successfully and Web URLs are not yet set.
Steps
Go to Web Service URL tab and click APPLY.
Note: Once applied, you will see a link on the same page.
Similarly go to Web Portal URL tab and click APPLY.
Note: Once applied, you will see a link on the same page. The virtual directory is actually sub directory for accessing Power Bi Report Server web portal.
Things to keep in mind.
Database should be SQL Server 2012 or later.
Port 80 must be allowed in Firewall for inbound traffic.
Port 80 must be forwarded in the modem.
You must have public Static IP from your ISP.
Now you can check for localhost as http://localhost/virtual-directory and hopefully it will work, then you can check with your public static ip like http://your-public-static-ip/virtual-directory where in this case virtual_directory is Reports from step 2.
Examples
In case if virtual_directory is Reports from step 2.
For Local: http://localhost/Reports
For Public: http://your-public-static-ip/Reports
My laptop and android mobile are connected to same router. I am able to access wamp running on my laptop using http://192.168.1.108/ but i want to access it like http://test.192.168.1.108/.
Any ideas?
My suggestion is to get a DNS service like noip.com. You can get an DNS address of whatever is available and point to a server in your own network, i.e. 192.168.1.108. I do this all the time.
I am using Macbook air and its OS is OS X 10.8.5, installed win7 with virtual box.
And developing web application at win7 virtual box, I want to port forward virtualbox
port to host port. So that I could test app on the host and also to the mobile phone
using same wifi.
First I didn't type host and guest ip and put the port value 8000.
I figured out guest ip and host ip by writing "ipconfig" and "ifconfig".
After running server of guest, I wrote the web address on host browser like below,
http://[guest ip]:8000/
But cannot load the web page of guest.
What is the problem?
And also if I want to load the web application of virtualbox to mobile phone
How could I do it?
Though it looks a bit silly, It would be glad to have an advice.
Thanks in advance :)
I would not recommend you to work that way, you can develop your web application right in your OSX, it would be much easier.
But if you have to do that way. Then first, because your network configuration is NAT, your VM will has an private IP like: 10.0.2.15, you need to forward to port to access, it likes:
From the above image, I forward port 2022 to 22, 2080 to 80 (web server)
So let's say your web is running at the same port 80, here is the URL for you to access to your web: 127.0.0.1:2080
BTW for me i don't like to work through the port forwarding, I prefer to configure my VM using "host only". By that way you can have an ip like 192.168.x.x and you can forget the port forwarding. You can read it more from here:
https://www.virtualbox.org/manual/ch06.html#network_hostonly
Hope it helps you.
I have a problem with deploying my web service in our Web server. In my
development machine (inside of our LAN), everything works fine. When I move
the application into our Web server (public addressed), I always get the
timeout exception. while i connecting the web service through my web browser it works fine with no issues, but through application am getting the timeout error. My app connects to our database server (inside of our LAN) to get statistical data in form of datasets. can i know the issue about this point.
That is most likely a firewall/port forwarding issue.
Did I understand you correctly: Your client application connects to the database server directly?
You should check which port you are using to connect to the database server.
Then check if the web server has an active firewall and if so, configure it properly to accept connections on that port.
You can always easily check if a port is open and reachable by using telnet:
On the command line type telnet MY_IP MY_PORT.
If a connection can be established the port is open.
For testing purposes, I'm trying to run a number of client applications connecting to a server all on the same host machine.
The host machine is running Windows 2008 Server Standard 32-bit with Service Pack 2.
On my XP development machine I installed the Microsoft Loopback Adapter in order to run multiple clients connecting from separate IP addresses. My LAN network is 192.168.1.xxx and so I chose 192.168.5.xxx for the loopback adapter addresses.
On my development machine, everything works fine and I am able to see the client applications binding to the loopback adapter using TCPView.
When I try and run the same setup on the Windows 2008 server with the same settings, the client applications are unable to bind to the loopback adapter addresses. There is no activity in TCPView and so I believe there's possibly some configuration setting I'm missing in setting up the loopback adapter.
Can anyone help?
Thanks!
Nick.
Ok, problem solved. I was specifying that the client connect to 127.0.0.1 but when I asked it to connect to a 192.168.5.x address it worked. The server was bound to 0.0.0.0 which suggests that it should still have been bound to 127.0.0.1 anyway but it just didn't seem to work!