Is there a file where I can manually change the "Local Network Address" that shows up in the Network Settings page for a network?

I have two network cards on two different networks
A. 192.168.1.0
B. 192.168.0.0
Only when I disable network card B do I succeed in setting up my site with the ability to access it over the internet. Once I re-enable network card A, the Local Network Address defaults to the A network and I loose connectivity.

How can I ensure that the network card that HttpVPN uses is the one on the B network?

Thank you for your response. On re-reading I realised that I made an error. It probably wouldn't change your answer too much, but just for the sake of clarity.

I have two network cards on two different networks
A. 192.168.1.x
B. 192.168.0.x
Only when I disable network card B do I succeed in setting up my site with the ability to access it over the internet. Once I re-enable network card B, the Local Network Address defaults to the B network and I loose connectivity.

So I tried using a metric for each card.

Card A is the one with direct access to the internet/modem and where HttpVPN works. I want this one to be the default so I assigned a metric of 1.

Card B's IP address is 192.168.0.1 and it was assigned by default when the internet connection sharing wizard was run in order for my Wireless Access Point to give internet to my wireless devices. I assigned this card a metric of 2.

When HttpVPN network was deleted and re-setup at https://MyOwnSecureWeb.com the Local Network Address still defaulted to the IP of card B, i.e. 192.168.0.1. once both network cards were enabled So setting the metric did not help.

I need the Local Network Address to default to IP of card A (192.168.1.x) otherwise I cannot view my webpage externally. Any other suggestions on how I can achieve this??

Thanks again for your response.

Your suggestion, unfortunately didn't work.

We've tried putting entries in the hosts file and lmhost file. I'm not exactly clear on what the lmhosts file does, but I tried it anyway. Neither worked.
When we ping the machine name, the ip it resolves to is 192.168.0.1. If we can get the machine name to resolve to 192.168.1.12 that might help. If there is no other way, we'll be waiting for Beta 2.

Thanks
To-nee-T

I restarted the machine when I made the changes and hoped that the HttpVpn service got restarted. I'll try this again though, but is there another way to restart the HttpVpn service?

Hi there.

The workarounds we have provided are not likely to succeed because after examining the logic of the proxy it is clear that our logic assumes that the first NIC found in the system determines which addresses are LAN and which are not. We are going to change the logic to look for all adapters that have IP addresses within private subnets (10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255, 192.168.0.0 - 192.168.255.255). We will try to add it into the upcoming Beta 2, but cannot guarantee that right now. We'll post here whether this change will be available soon.

Also, we assume that the application you are hosting with HttpVPN has a URL that resolves to the A network (192.168.1.x). Could you please confirm that? Otherwise the problem may be something else.

Best regards,
UltiDev Team.

Message was deleted by a User.

Message was deleted by a Moderator.

Message was deleted by a Moderator.

Message was deleted by a Moderator.

Message was deleted by a Moderator.