Posted on

Disabling Skype To Use, Open And Listen On Port 80 As Well As 443 On Local PC

Disabling Skype To Use, Open And Listen On Port 80 As Well As 443 On Local PC

If you really want to install any web server, or maybe an application that requires web pages which is to be served through common HTTP or may be HTTPS ports, i.e. on port 80 as well as on port 443, an error message may appear and suggest that port 80 or port 443 was in use or is being occupied by any other application. It could also happen when there is no web server like Apache or IIS currently installed or running on that system.

While trying to investigate this issue by identifying the application that is being used on port 80, we suspect that the root cause might be due to Skype which allows the users to use the port 80 and the port 443 for alternatives as incoming connections. It uses port 80 as well as 443 for allowing Skype behind firewall in order to connect to the peers or to accept incoming connection with peers though NAT. This wouldn’t be able to connect through the restrictions or firewall that block other ports from opening.

Skype that listens, opens and occupies port 80 as well as port 443 may prevent other applications that require such port for working properly. So, the ability of the Skype for using port 80 as well as port 443 has to be stopped immediately, turned off and it should also remain disabled.

In order to turn off for disabling Skype usage for and listening on the port 80 as well as port 443, we have to open Skype window, after that click on the menu for Tools and then select Options. Then click on the Advanced Tab, after that go to the Connection sub-tab. Here Untick or uncheck that check box for the use port 80 as well as 443 for alternatives of incoming connections option. Lastly, click on the Save button then restart the Skype for making the change effective.

Posted on

Windows VirtualPC Network NAT Mode Cannot Connect To Internet Problem

How to Connect To Internet in Windows XP Guest OS in Virtual PC with NAT

While using Network Address translation or NAT adapter on virtual PC 2007, by using Windows XP as the guest OS, it has been notice that the system does not get connected to the Internet. Then you will find it unable to use the system for browsing the websites with any of the web browsers, like the Internet Explorer and Firefox.

The problem while trying to connect to the Internet with the virtual machine having guest OS of Windows XP, takes place for no real reason, which is in spite the networking with NAT adapter working prior to the trouble occurrence.

However, some connections via protocols that do not call for domain name of translation, for instance secure FTP, FTP, SSH or telnet to remote server over Internet by means of IP address as an alternative host name, seem to work just fine.

The trouble seems to lie in Windows XP (which is functioning as a guest operating system) due to wrong DNS server which gets automatically assigned. The fault may also occur if the user had entered the incorrect IP address of the DNS server.

In this case, first confirm that the DNS server is really resolving a URL or domain name properly. Otherwise, you have to change it to the correct the DNS Server address in guest operating system of the virtual machine as per the DNS Server address entered in host operating system.

There could be another reason for the above problem, which is wrong assignment by the virtual networking adapter. If the network connection properties for TCP/IP protocol is set to obtain DNS server address automatically then the virtual NAT router will assign and allocate the same DNS server that’s been used by host operating system to guest operating.

Nevertheless, for some causes, the DNS server used might be wrong or invalid, such as in the case when the user switches or changes Internet connection which have dissimilar DNS server, or when user changes the Internet connection to new DNS servers devoid of restarting the horde computer.

What the come across this type of issue, you need to first shut down the virtual machines, and then restart Microsoft Virtual PC. The error will be fixed following that. Just in case you’re unable to shutdown the guest operating system for any reason, you have to configure and set a fixed DNS Server IP address manually in the TCP/IP Properties for Local Area Network (LAN) Connections.

Note: – If you are going to install Windows Server 2003 or 2008 or Windows Vista as a guest operating system in your virtual machine of VPC, then there will one more DNS Server caused, and it is not capable to connect or browse the internet. In such a case, the resolution to the issue would be to do manual settings for the DNS Server IP address, the IP address should be set as 192.168.131.254.