I set up a virtual server with VMWare running Windows Server 2008 R2.
The hosting machine is my desktop computer with windows 10.
I set up everything and internet connection on my server is working correctly and if I check localhost or static ip on server side, I see the IIS7 home page.
My problem appens when I try to reach this page with the public ip of my machine.
I checked on no-ip and also on websites which tells you the public IP of your desktop. Now I tryed to navigate to this ip but neither from the server itself, neither from hosting machine or external net I can find my site.
What I tryed:
Disabled all firewalls on server
Disabled all firewalls on hosting desktop pc
Set up on VMWare the connection as Bridge
I also searched on the net but I don't really know how to make my server visible with his public ip.
Those are my VMWare settings:
If you need something else, ask freely.
Any help will be appreciated, thanks all.
Related
I am trying to access the SSRS web portal. I have SQL Server and Report Server installed on laptop with Windows 10. I want to access this from another laptop running windows 11 that is connected to the same home internet network.
The web portal works fine when I access it from the computer running Report Server:
But when I try to access the url from another the other computer on the same network, the page just doesn't load:
I tried to follow the instructions from this site: https://askgarth.com/blog/why-cant-i-access-my-ssrs-site-remotely/
I opened port 80 TCP protocol in windows firewall to allow connections.
I think that the issue may be the profile to which the rule applies:
The instructions I tried to follow said to open up the Domain. I also tried the Private option and still no luck.
I'm nervous about opening up ports on my firewall. But how can I set this up to access the Report Server from another computer on my network?
I've just checked my setup which is basically the same...
'Server' Desktop running Windows 10 Pro: Hosts SQL Server 2019 and SSRS
'Client' Desktop running Windows 11: Accessing SSRS from here
I checked the 'server' PC and the only SQL specific ports that are open are TCP port 1433 to allow me to access the database engine via SSMS etc from the 'client' PC and TCP port 80 (both are setup to domain + private although domain should be irrelevant)
I don't normally access the SSRS portal from the 'client' but it did work in as far as it said I do not have access to any reports, but it was showing the web portal page itself just fine.
You have probably done all this but here are a few things you could try...
Check if your version of Win10 is supported. If it's Win10 home for example it may not support everything required but this is just a guess.
Ping the server from the host and make sure you get a response (assuming PING response has not been turned off)
Check server firewall allows incoming on ports TCP 80 and TCP 1433 (1433 should not be required but you can always switch this off later)
Attempt access using the server ip e.g. http://192.168.1.123/Reports
If this all fails, turn off the windows firewall and test again. You can always disconnect your router from the internet whilst you do this to be safe. If this works then you at least know it's a firewall issue.
Check if you have any 3rd party anti-virus software that might be acting as a firewall - turn off and test again.
I don't think that we can share the link that we get from the live server extension to someone else for viewing our web page.
kindly advise me. I am new to front-end development.
By default LiveServer will listen for network connections on 127.0.0.1 and is available only to clients running on the same computer.
You can change that in the settings (under Live Server > Settings:Host) to specify any IP address allocated to the computer you are working on. You can also use 0.0.0.0 for every IP address allocated to that computer.
Anyone who can reach the IP address you select (which is typically anyone on the same LAN as you) can then visit http://192.0.0.10:5500/ to see the site. (Replace the IP address in that example with the one assigned to your computer that you selected above).
For someone to access the server from a different network, you will need to have an IP address on the public Internet. Typically you would get this by following the above instructions and then configuring your router to forward port 5500 from its Internet facing IP address to the IP address of your computer on the LAN.
You can also look at tunnelling a connection with by creating an SSH tunnel manually or using a service like ngrok which connects a URL on the public Internet to your local server (note that this removes the requirement to change the Live Server configuration away from 127.0.0.1).
I'm seeing this problem connecting to most sites when connected to our office LAN.
I'm running a VM (using VMWare Workstation 15 Player) running Win10. The host is also Win10.
Your connection is not secure
The owner of www.google.com has configured their web site improperly. To protect your information from being stolen, Firefox has not connected to this web site.
This site uses HTTP Strict Transport Security (HSTS) to specify that Firefox only connect to it securely. As a result, it is not possible to add an exception for this certificate.
Advanced shows
Error code: SEC_ERROR_UNKNOWN_ISSUER
The network connection is "NAT: Used to share the host's IP address".
I had Avast installed and uninstalled it so ensure it was not blocking the connections.
I do not get this error on the host machine
If I connect the host machine to our corporate VPN or use a Wifi connection, I do not get this error.
The date and time are also correct.
Is there something that VMWare Player is doing to the connection?
Firefox Quantum 65.0.2
Chrome Version 72.0.3626.121
Chrome
Firefox
This is my scenario,
I have a Ubuntu 12.10 host and a win 7 guest installed in the virtual box. The Network is configured to be NAT in the virtual box. I have a mysql sever installed in the Ubuntu with “bind_address” in my.cnf is commented out.
How can I access this mysql server from the windows 7 guest? I did some search in Google and came accross with this Host-Only Networking With VirtualBox but I cant get it work as I don't have statics IP with my internet vendor and my network knowledge is very bad. All I know is that I have DHCP enabled Internet connection. So if i do any IP's in the network settings I don't have Internet.
I know that there are plenty of solutions on the other way around (access the guest server from the host) but still cant figure it out.
So any help is appreciated.
Thanks
Your external IP being static or not has no bearing to accessing a virtualized server on your LAN.
Set VirtualBox to bridge mode.
Simply determine your computer's DHCP-selected internal IP (usually 192.168.1.SOMETHING) and replace the last number with another that is less than 250. For example, if your computer was 192.168.1.6, 192.168.1.70 would work fine on the VM(pick a high number to void conflicts).
Set it by using the control panel->adapter settings. Reboot the VM. Connect to MySQL at 192.168.1.70(or the address you picked earlier).
Note: If your computer's address is in a different subnet (192.168.0.XXX, 10.XX.XX.XX, etc) change the last number and keep the first numbers the same as on the host.
I have 2 servers srv-erp1 and srv-erp3. I made them mirror on each other. All setup is done by lots of tutorials and examples.
But when I call
ALTER DATABASE MIRROR_TEST SET PARTNER = 'TCP://srv-erp3:5022'
It`s response is:
The server network address "TCP://srv-erp3:5022" can not be reached or
does not exist. Check the network address name and that the ports for
the local and remote endpoints are operational.
I go to cmd on srv-erp3 and use netstat -an... this port is listening.
I go to cmd on srv-erp1 and use telnet srv-erp3 5022...and its ok to connect.
All firewalls are turned off. The only difference in config of srvrs is that srv-erp1 is on Windows Server 2003 R2 x64, and srv-erp3 is on Windows 2008 R2 x64
What can be the reason of this problem?
Regards, Dmitry.
I have such problem, the solution was using certificates. My problem appeared because my servers were not in one domain.