777 not working anymore?

Something strange- it used to work, Mac or Windows. Just dial, and it gets an IP. IT still does except no valid DNS is passed, nothing resolves. The connection just hangs there like a dead DSL line with a link light.

Anything change recently?

Im using a Sanyo 8100. This started a couple months ago and I just wrote it off to a fresh Windows install, but even with Mac OS X, which it was simpler to get going than Windows, it does the same thing.

---

› See More: 777 not working anymore?

Doesn't work for me either- anymore, same/similar setup.

I even tried doing manual DNS entries, no ping, traceroute, etc. All
packets stop at the IP# assigned, the status will show me having an IP
of 172.x.x.x assigned on the Mac which makes no sense, thats usually a
private IP range.

This is after the connection is established and authentication passed.
I've tried with the user/pass web/web and leaving it blank.

[email protected] wrote:
>
> Doesn't work for me either- anymore, same/similar setup.
>
> I even tried doing manual DNS entries, no ping, traceroute, etc. All
> packets stop at the IP# assigned, the status will show me having an IP
> of 172.x.x.x assigned on the Mac which makes no sense, thats usually a
> private IP range.
>
> This is after the connection is established and authentication passed.
> I've tried with the user/pass web/web and leaving it blank.

What phone?

Notan

Sanyo 8100 and 8200 here. I have a couple of them.

On Wed, 12 Oct 2005 22:45:14 +0200 (CEST), George Orwell
<[email protected]> wrote:

>Something strange- it used to work, Mac or Windows.
>Just dial, and it gets an IP. IT still does except no valid DNS is passed, nothing resolves.
>The connection just hangs there like a dead DSL line with a link light.

As of this afternoon, mine seems to be working. I'm getting about 85
kbit/sec from dslreports.com, which is actually pretty good for this
area.
Joe Huber
[email protected]

On one Windows machine I only get http/https, no ssh, to ping, no
imaps, etc.

Same phone, a more recent FutureDial install (same version of the
software, but installed much later) on a different machine everything
works.

<[email protected]> wrote in message
news:[email protected]...
> Doesn't work for me either- anymore, same/similar setup.
>
> I even tried doing manual DNS entries, no ping, traceroute, etc. All
> packets stop at the IP# assigned, the status will show me having an IP
> of 172.x.x.x assigned on the Mac which makes no sense, thats usually a
> private IP range.

A 172 is usually assigned by the PC when no other IP is assigned (if you
have DNS/DHCP active as a service in XP). This almost always tells me that I
have not reached my ISP.