I just posted along the same line. I am having the same issue. Can
connect to GoogleWifiSecure just fine from my roof top AP, but nothing
resolves. I think there is something wrong w/ name resolution on
google wifi network. So I am also w/ network done where I live.
On Apr 8, 9:21 am, bethric <wolffe...@gmail.com> wrote:
> Sadly, here is the situation as of this morning -- I'm back on my
> blackberry tether...
> - left rooftop AP and home router powered down all night -- from 9pm
> to 5.40am.
> - Still cannot get connected after bringing everything up this
> - Seems to be a name serving or other similar problem -- if I tracert
> to 18.104.22.168 or 22.214.171.124, the timeouts begin at the Google AP
> - FYI my rooftop AP does have various commands, etc, DHCP renew, etc.
> On Apr 7, 8:58 pm, wifi4all <wifi4...@gmail.com> wrote:
> > Just to add on....
> > The reason I recommended shutting the AP down for an hour is to time
> > If your connection device (your rooftop AP) can send a DHCP Release,
> > WiFi4All
> > On Apr 7, 8:53 pm, wifi4all <wifi4...@gmail.com> wrote:
> > > Hi,
> > > What do you get when you do a traceroute to the default router ?
> > > The only thing I can think of is that you are getting 'black
> > > The system is keyed on the DHCP protocol. Can you force a DHCP
> > > WiFi4All
> > > On Apr 7, 8:15 pm, bethric <wolffe...@gmail.com> wrote:
> > > > Right now I'm using my mobile phone tethered but since this morning we
> > > > GoogleWiFi Node: 1170 Spencer Court
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.