Can't gain access to remote web access

[MAD4TECH 0]

You can't use that address from inside your LAN. You have to use the server's LAN IP, probably a 192 address, such as https://192.168.0.101.

 

Try getting your g/f to try https://82.26.94.188. it should work for her.

 

Hi we have success she was able to gane access she said that when she put the ip in it showed that this page was un know she clicked ok and the page showed up and loged in so how do i get my domain working?

and thank agane

[jmwills 284]

The 82.x address works.

 

DNS names are updated globally and should not be in this much of a lag. Just tried the DNS, and it is still not resolving.ut rather

 

This issue is not yours, but rather your ISP's

 

You can't use that address from inside your LAN. You have to use the server's LAN IP, probably a 192 address, such as https://192.168.0.101.

 

This depends on the router. I can go out and come back in to mine.

[ikon 439]

Hi we have success she was able to gane access she said that when she put the ip in it showed that this page was un know she clicked ok and the page showed up and loged in so how do i get my domain working?

and thank agane

 

The unknown page was warning her the page has an unverifiable certificate. It's not a problem, except that you will have to warn anyone who wants to come to your site to ignore/acknowledge the warning.

 

As jmwills said, the issue is not really yours, it's an internet DNS resolving issue. It can take up to 72 hours for a domain IP change to completely propagate, but that is rare; it usually happens in a matter of a few hours.

[MAD4TECH 0]

The 82.x address works.

 

DNS names are updated globally and should not be in this much of a lag. Just tried the DNS, and it is still not resolving.ut rather

 

This issue is not yours, but rather your ISP's

 

You can't use that address from inside your LAN. You have to use the server's LAN IP, probably a 192 address, such as https://192.168.0.101.

 

This depends on the router. I can go out and come back in to mine.

so it a problerm wilth my internet service provider then? do i turne off UPnP off now then?

[jmwills 284]

UPnP has nothing to do with the DNS issue. Turn it off since it is a big security risk.

[MAD4TECH 0]

 

The unknown page was warning her the page has an unverifiable certificate. It's not a problem, except that you will have to warn anyone who wants to come to your site to ignore/acknowledge the warning.

 

As jmwills said, the issue is not really yours, it's an internet DNS resolving issue. It can take up to 72 hours for a domain IP change to completely propagate, but that is rare; it usually happens in a matter of a few hours.

 

Cool thanks so forgive me if i am being dumb but will the domain name sort its self out and shuld i turn off UPnP off now?

[ikon 439]

This issue is not yours, but rather your ISP's

 

I'm wondering if it's an issue at MS. MS is the authoritative source for homeserver.com, is it not? If it is, what happens if it doesn't get updated about an IP change? Perhaps MAD4TECH needs to force his server to update MS. I'm not sure how to make it do that - perhaps just turn off Remote Access and then turn it back on?

 

You can't use that address from inside your LAN. You have to use the server's LAN IP, probably a 192 address, such as https://192.168.0.101.

 

This depends on the router. I can go out and come back in to mine.

 

I'm aware, but I've found that the number of routers that allow loopback is pretty small.

[jmwills 284]

He could put and additional DNS setting in the adapter for Google which is 8.8.8.8

 

It's not Microsoft or mine would not resolve (which it does). https://willsit.homeserver.com

[ikon 439]

Cool thanks so forgive me if i am being dumb but will the domain name sort its self out and shuld i turn off UPnP off now?

 

I would not turn off UPnP until the URL resolving issues are fixed - let's tackle 1 thing at a time.

 

What I suggest now is to turn off Remote Web Access, wait 5 minutes, then turn it back and go through the process. Hopefully, this will force Microsoft to see the new IP.

 

It's not Microsoft or mine would not resolve (which it does). https://willsit.homeserver.com

 

Not sure what you're thinking. My thinking is that the new IP will never get propagated until the MS mothership is updated and sends out an IP change notification. And MS won't get updated until the server sends out an update to MS.

[jmwills 284]

True, but the update is beyond his control unless he puts in additional DNS resources.

 

I'd still turn off UPnP and configure it manually. His router, as some do, might have issues with it.