I've got a Windows Server test environment installed as a VM on another company server (e.g. 192.168.2.30) which currently hosts about five different test sites. My local machine contains a line in the hosts file linking the IP address of the test environment to dev.company.com. The first site we made (linked to port 80) works perfectly as it's the default port.
However, we are unable to access our other websites on other ports (i.e. dev.company.com:81), although we can access them just fine on our test environment through 192.168.2.30:81. My understanding is that the hosts file doesn't do anything to ports, which is why I'm confused as to why it wouldn't work as such.
What I want is to be able to create a number of different sites in IIS on different ports, and for users on the same network to be able to access them through the dev.company.com alias by adding the port number at the end.
How can I modify my test environment and my local machines to allow this to work?
EDIT: As stated by joeqwerty it would appear to be a firewall issue. How would I get the Windows Firewall on the server to allow ports 80-100 to be free?