It sounds like your network settings and how you have traffic setup...
You need to setup a bridge to connect the lan adapter (which hfs is serving) and the virtual wifi hotspot
http://windows.microsoft.com/en-us/windows-vista/what-is-a-network-bridgeYou might need to set hfs to a different custom ip address ie the ip address scheme that the virtual hotspot will be giving.
It could be that you vitural hot spot isn't giving out ip within hfs range ie, your network of ip address in 1`92.168.173 contest to the virtual hospot firewall preventing web traffic.
--So let break down your network and see if we can't find the kick in the chain
---
You have your "hfs" server machine which connects to a router getting ip address schema of:
I'm assuming unless otherwise noted:
(hfs server machine cmd command: ipconfig /all > echo network adapters and info.log) - which will save the output of your hfs network setting and basic lan /wifi/ virtual adapter if any)- either public post or private message it )
Or confirm the setup i write below:)
Router dhcp range: 192.168.173.1-192.168.173.255
subnet (classs C) 255.255.255.0
(since you are using the 192.168.173.1 ip address you might be causing network issue as sometimes ".1" is reserved as a gateway (and/or these ip address: / .255 is reserved for the broad cast / and.0 is reserved for other traffic...)
(I think you are using your Broadcast address)So first lets Change your hfs service ip to something like 192.168.173.x (x being 2-254)- does that fix your issue?
then its a routing issues because you were on a reserved ip address
http://en.wikipedia.org/wiki/Reserved_IP_addresseshttp://en.wikipedia.org/wiki/Subnetwork#IPv4_subnettingso the the virtual wifi hotspot is either a virtual wifi vlan in the router or an adapter on you windows machine...
--If it is in the router (you need to add the lan that your hfs server is in to complete proper networking--
--If it is on the windows side, (we bridge the network adapters) highlight the wifi adapter and the lan adapter and right mouse click bridge connection---
Once we verify that the virtual address has acquitted access to each other (test by running pings commands across the adapters to gateways and computer connected...
---
i believe it is an issues with how you have your network setup, and you may need to supply a "dmz" and have multi-connections or forms of connection to allow adequate network communication form your virtual hot spot and the hfs machine)
You orgianl post doesn't share anyinfo that you were tryign to comunicate across vituarl interfaces, adn the hfs "onscreen" log didn't show much...
More inforamtion is required to help you further..
Recap:
1.) Change your hfs server machine ip address so it is not on nor using the 173.1 address depends on your subnet...
2.) double check you network setting on your virtual wifi hotspot to make sure the hfs server machine is getting an ip form it or is able sending some information that way. (ping command)
3.) attempt to explain how your network is setup so user or myself are able to go through and see what device where is needing check and correcting settings...
----
Example:
(ISP Internet) > (off brand router) > HFS Machine
Client Machine (the machine connecting to hfs) > (off brand router) > HFS Machine
----
Where is you virtual hot-spot and where does it take play in your network?...
