Internet connection woes

I’m having trouble getting the Windows installed version of RtP to work
with my ISP.

I seem to dial up and connect correctly and I stay connectted for as
long as I want. But Voyager cannot display any web sites. I get a page
from “yournamefree.com” or some such site that says “www.qnx.com is
taken but you can register your web address at bla, bla, bla…”. If I
use Win98 on that PC everything works (as good as Win98 ever does :wink:)
so the hardware works.

I opened a terminal window and I can ping both of the ISP’s DNS’s
addresses with no problem. If I try to ping anything else I get the
address “208.184.130.60” on the ping listing (which seems to be
yournamefree.com”).

So what am I overlooking, I have even looked at the help system so I did
RTFM, but maybe not the right parts?

Thank you for your help.

Gerald Bonnstetter <bonnsoft@netins.net> wrote:

I’m having trouble getting the Windows installed version of RtP to work
with my ISP.

I seem to dial up and connect correctly and I stay connectted for as
long as I want. But Voyager cannot display any web sites. I get a page
from “yournamefree.com” or some such site that says “> www.qnx.com > is
taken but you can register your web address at bla, bla, bla…”. If I
use Win98 on that PC everything works (as good as Win98 ever does > :wink:> )
so the hardware works.

I opened a terminal window and I can ping both of the ISP’s DNS’s
addresses with no problem. If I try to ping anything else I get the
address “208.184.130.60” on the ping listing (which seems to be
yournamefree.com”).

So what am I overlooking, I have even looked at the help system so I did
RTFM, but maybe not the right parts?

What happenes if your “ping 209.226.137.53” ? Or try a “traceroute -n 209.226.13.7.53”.
My guess is your ISP’s DNS gone crazy…

-xtang

Xiaodan Tang wrote:

Gerald Bonnstetter <> bonnsoft@netins.net> > wrote:
I’m having trouble getting the Windows installed version of RtP to work
with my ISP.

I seem to dial up and connect correctly and I stay connectted for as
long as I want. But Voyager cannot display any web sites. I get a page
from “yournamefree.com” or some such site that says “> www.qnx.com > is
taken but you can register your web address at bla, bla, bla…”. If I
use Win98 on that PC everything works (as good as Win98 ever does > :wink:> )
so the hardware works.

I opened a terminal window and I can ping both of the ISP’s DNS’s
addresses with no problem. If I try to ping anything else I get the
address “208.184.130.60” on the ping listing (which seems to be
yournamefree.com”).

So what am I overlooking, I have even looked at the help system so I did
RTFM, but maybe not the right parts?

What happenes if your “ping 209.226.137.53” ? Or try a “traceroute -n 209.226.13.7.53”.

\

ping 209.226.137.53

PING 209.226.137.53 (209.226.137.53): 56 data bytes

— 209.226.137.53 ping statistics —
11 packets transmitted, 0 packets received, 100% packet loss

traceroute -n 209.226.137.53

traceroute to 209.226.137.53 (209.226.137.53), 30 hops max, 40 byte
packets
1 167.142.174.234 152 ms 147 ms 145 ms
2 167.142.174.233 150 ms 150 ms 146 ms
3 167.142.53.221 157 ms 152 ms 150 ms
4 167.142.57.65 169 ms 153 ms 154 ms
5 157.130.96.145 172 ms 183 ms 167 ms
6 146.188.209.114 181 ms 181 ms 181 ms
7 146.188.208.126 182 ms 179 ms 179 ms
8 146.188.209.145 177 ms 184 ms 175 ms
9 157.130.107.110 173 ms 174 ms 178 ms
10 206.108.103.121 181 ms 176 ms 174 ms
11 206.108.103.113 219 ms 218 ms 212 ms
12 206.108.98.54 244 ms 226 ms 227 ms
13 206.108.99.154 228 ms 218 ms 229 ms
14 209.226.137.126 238 ms 235 ms 223 ms
15 209.226.137.53 251 ms 238 ms 232 ms

<<<

So ping does not work and traceroute does. Strange, and I can ping
209.226.137.126 but not 209.226.137.53 that is one hop more.

But I am getting somewhere after I took the -n option off of traceroute,
then I saw you were having me ping “www.qnx.com”. So I tried
“traceroute www.qnx.com” and got:


traceroute > www.qnx.com

traceroute to www.qnx.com.bonnsoft.com (208.184.130.60), 30 hops max, 40
byte packets
[and lots trace junk…]
<<<

So it looks like RtP may be adding “.bonnsoft.com” onto the name. So
I’ll see if I can fix this by taking “bonnsoft.com” out of the network
configuration tomorrow when I look at it again.

My guess is your ISP’s DNS gone crazy…

Works for Win98, NT and Linux. :wink:

-xtang

Gerald Bonnstetter <bonnsoft@netins.net> wrote:


Xiaodan Tang wrote:

Gerald Bonnstetter <> bonnsoft@netins.net> > wrote:
I’m having trouble getting the Windows installed version of RtP to work
with my ISP.

I seem to dial up and connect correctly and I stay connectted for as
long as I want. But Voyager cannot display any web sites. I get a page
from “yournamefree.com” or some such site that says “> www.qnx.com > is
taken but you can register your web address at bla, bla, bla…”. If I
use Win98 on that PC everything works (as good as Win98 ever does > :wink:> )
so the hardware works.

I opened a terminal window and I can ping both of the ISP’s DNS’s
addresses with no problem. If I try to ping anything else I get the
address “208.184.130.60” on the ping listing (which seems to be
yournamefree.com”).

So what am I overlooking, I have even looked at the help system so I did
RTFM, but maybe not the right parts?

What happenes if your “ping 209.226.137.53” ? Or try a “traceroute -n 209.226.13.7.53”.

\

ping 209.226.137.53

PING 209.226.137.53 (209.226.137.53): 56 data bytes

— 209.226.137.53 ping statistics —
11 packets transmitted, 0 packets received, 100% packet loss

traceroute -n 209.226.137.53

traceroute to 209.226.137.53 (209.226.137.53), 30 hops max, 40 byte
packets
1 167.142.174.234 152 ms 147 ms 145 ms
2 167.142.174.233 150 ms 150 ms 146 ms
3 167.142.53.221 157 ms 152 ms 150 ms
4 167.142.57.65 169 ms 153 ms 154 ms
5 157.130.96.145 172 ms 183 ms 167 ms
6 146.188.209.114 181 ms 181 ms 181 ms
7 146.188.208.126 182 ms 179 ms 179 ms
8 146.188.209.145 177 ms 184 ms 175 ms
9 157.130.107.110 173 ms 174 ms 178 ms
10 206.108.103.121 181 ms 176 ms 174 ms
11 206.108.103.113 219 ms 218 ms 212 ms
12 206.108.98.54 244 ms 226 ms 227 ms
13 206.108.99.154 228 ms 218 ms 229 ms
14 209.226.137.126 238 ms 235 ms 223 ms
15 209.226.137.53 251 ms 238 ms 232 ms



So ping does not work and traceroute does. Strange, and I can ping
209.226.137.126 but not 209.226.137.53 that is one hop more.

That’s my fault. “ping” is not working on 209.226.137.53, but
as you can see, your connection is OK.

But I am getting somewhere after I took the -n option off of traceroute,
then I saw you were having me ping "> www.qnx.com> ". So I tried
"traceroute > www.qnx.com> " and got:


traceroute > www.qnx.com

traceroute to > www.qnx.com.bonnsoft.com > (208.184.130.60), 30 hops max, 40
byte packets
[and lots trace junk…]


So it looks like RtP may be adding “.bonnsoft.com” onto the name. So
I’ll see if I can fix this by taking “bonnsoft.com” out of the network
configuration tomorrow when I look at it again.

Hm, this bother me a little.
It should only add .bonnsoft.com if it faild to find “www.qnx.com
at first place…
Check you “/etc/resolv.conf”, if there is one (by default, there
is none, unless you create one).
Check the “phlip”, see if anything is strange.
Try this:

  1. nslookup
  2. server <you ISP’s DNS server ip>
  3. www.qnx.com

This will ask your DNS server about www.qnx.com, see if they
solve it correct.

If you still get in trouble, try to post/email me your
/etc/resolv.conf (if exist)
/etc/net.cfg

-xtang

Xiaodan Tang wrote:

Gerald Bonnstetter <> bonnsoft@netins.net> > wrote:

Xiaodan Tang wrote:

Gerald Bonnstetter <> bonnsoft@netins.net> > wrote:
I’m having trouble getting the Windows installed version of RtP to work
with my ISP.

I seem to dial up and connect correctly and I stay connectted for as
long as I want. But Voyager cannot display any web sites. I get a page
from “yournamefree.com” or some such site that says “> www.qnx.com > is
taken but you can register your web address at bla, bla, bla…”. If I
use Win98 on that PC everything works (as good as Win98 ever does > :wink:> )
so the hardware works.

I opened a terminal window and I can ping both of the ISP’s DNS’s
addresses with no problem. If I try to ping anything else I get the
address “208.184.130.60” on the ping listing (which seems to be
yournamefree.com”).

So what am I overlooking, I have even looked at the help system so I did
RTFM, but maybe not the right parts?

What happenes if your “ping 209.226.137.53” ? Or try a “traceroute -n 209.226.13.7.53”.

\

ping 209.226.137.53

PING 209.226.137.53 (209.226.137.53): 56 data bytes

— 209.226.137.53 ping statistics —
11 packets transmitted, 0 packets received, 100% packet loss

traceroute -n 209.226.137.53

traceroute to 209.226.137.53 (209.226.137.53), 30 hops max, 40 byte
packets
1 167.142.174.234 152 ms 147 ms 145 ms
2 167.142.174.233 150 ms 150 ms 146 ms
3 167.142.53.221 157 ms 152 ms 150 ms
4 167.142.57.65 169 ms 153 ms 154 ms
5 157.130.96.145 172 ms 183 ms 167 ms
6 146.188.209.114 181 ms 181 ms 181 ms
7 146.188.208.126 182 ms 179 ms 179 ms
8 146.188.209.145 177 ms 184 ms 175 ms
9 157.130.107.110 173 ms 174 ms 178 ms
10 206.108.103.121 181 ms 176 ms 174 ms
11 206.108.103.113 219 ms 218 ms 212 ms
12 206.108.98.54 244 ms 226 ms 227 ms
13 206.108.99.154 228 ms 218 ms 229 ms
14 209.226.137.126 238 ms 235 ms 223 ms
15 209.226.137.53 251 ms 238 ms 232 ms



So ping does not work and traceroute does. Strange, and I can ping
209.226.137.126 but not 209.226.137.53 that is one hop more.

That’s my fault. “ping” is not working on 209.226.137.53, but
as you can see, your connection is OK.

But I am getting somewhere after I took the -n option off of traceroute,
then I saw you were having me ping "> www.qnx.com> ". So I tried
"traceroute > www.qnx.com> " and got:

\

traceroute > www.qnx.com

traceroute to > www.qnx.com.bonnsoft.com > (208.184.130.60), 30 hops max, 40
byte packets
[and lots trace junk…]


So it looks like RtP may be adding “.bonnsoft.com” onto the name. So
I’ll see if I can fix this by taking “bonnsoft.com” out of the network
configuration tomorrow when I look at it again.

Hm, this bother me a little.
It should only add .bonnsoft.com if it faild to find "> www.qnx.com> "
at first place…
Check you “/etc/resolv.conf”, if there is one (by default, there
is none, unless you create one).

There is no file “/etc/resolv.conf”.

Check the “phlip”, see if anything is strange.

I’m new to QNX, it looks ok but how would I know. :wink:

Try this:

  1. nslookup
  2. server <you ISP’s DNS server ip
  3. www.qnx.com

Bingo, it thinks it is the DNS or something like that:

nslookup

Default Server: hydra_qnx
Address: 0.0.0.0

www.qnx.com
Server: hydra_qnx

Address: 0.0.0.0

*** hydra_qnx can’t find www.qnx.com: No response from server

exit

<<<

If I do “nslookup - 167.142.225.3” with my ISP’s DNS then it finds
www.qnx.com ok.

So how to I tell it that it isn’t the default name server.


This will ask your DNS server about > www.qnx.com> , see if they
solve it correct.

If you still get in trouble, try to post/email me your
/etc/resolv.conf (if exist)

No file.

/etc/net.cfg

net.cfg was:

nto network config file v1.2

version v1.2

[global]
hostname hydra_qnx
domain bonnsoft.com
nameserver 167.142.225.3
nameserver 167.142.225.5
lookup file bind

[en0]
type ethernet
mode manual
manual_ip 192.168.0.31
manual_netmask 255.255.255.0
<<<<


-xtang

Gerald Bonnstetter <bonnsoft@netins.net> wrote:

Xiaodan Tang wrote:

There is no file “/etc/resolv.conf”.

This is OK, don’t worry. (actually this is good :slight_smile:

Check the “phlip”, see if anything is strange.

I’m new to QNX, it looks ok but how would I know. > :wink:

Try this:

  1. nslookup
  2. server <you ISP’s DNS server ip
  3. www.qnx.com

Bingo, it thinks it is the DNS or something like that:

\

nslookup

Default Server: hydra_qnx
Address: 0.0.0.0

www.qnx.com
Server: hydra_qnx
Address: 0.0.0.0

*** hydra_qnx can’t find > www.qnx.com> : No response from server
exit



If I do “nslookup - 167.142.225.3” with my ISP’s DNS then it finds
www.qnx.com > ok.

You should do a “server 167.142.225.3” in nslookup so that it will
go to your ISP’s DNS instead of 0.0.0.0, but anyway, you proved
that your ISP’s DNS is good. :slight_smile:

So how to I tell it that it isn’t the default name server.

This will ask your DNS server about > www.qnx.com> , see if they
solve it correct.

If you still get in trouble, try to post/email me your

/etc/net.cfg

net.cfg was:

\

nto network config file v1.2

version v1.2

[global]
hostname hydra_qnx
domain bonnsoft.com
nameserver 167.142.225.3
nameserver 167.142.225.5
lookup file bind

[en0]
type ethernet
mode manual
manual_ip 192.168.0.31
manual_netmask 255.255.255.0

Are you sure this is correct ? I haven’t see default route (gateway).
Are you using ppp ?
From the setting above, I can’t even see how you could ping to the
DNS server (167.142.225.3).
Also, please note you must be “root” to run phlip…

Another thing you could do is do a:

getconf CS_RESOLVE

cat /proc/ipstats

and post the output.

-xtang

Xiaodan Tang wrote:

Gerald Bonnstetter <> bonnsoft@netins.net> > wrote:
Xiaodan Tang wrote:

There is no file “/etc/resolv.conf”.

This is OK, don’t worry. (actually this is good > :slight_smile:

Check the “phlip”, see if anything is strange.

I’m new to QNX, it looks ok but how would I know. > :wink:

Try this:

  1. nslookup
  2. server <you ISP’s DNS server ip
  3. www.qnx.com

Bingo, it thinks it is the DNS or something like that:

\

nslookup

Default Server: hydra_qnx
Address: 0.0.0.0

www.qnx.com
Server: hydra_qnx
Address: 0.0.0.0

*** hydra_qnx can’t find > www.qnx.com> : No response from server
exit



If I do “nslookup - 167.142.225.3” with my ISP’s DNS then it finds
www.qnx.com > ok.

You should do a “server 167.142.225.3” in nslookup so that it will
go to your ISP’s DNS instead of 0.0.0.0, but anyway, you proved
that your ISP’s DNS is good. > :slight_smile:

So how to I tell it that it isn’t the default name server.

This will ask your DNS server about > www.qnx.com> , see if they
solve it correct.

If you still get in trouble, try to post/email me your

/etc/net.cfg

net.cfg was:

\

nto network config file v1.2

version v1.2

[global]
hostname hydra_qnx
domain bonnsoft.com
nameserver 167.142.225.3
nameserver 167.142.225.5
lookup file bind

[en0]
type ethernet
mode manual
manual_ip 192.168.0.31
manual_netmask 255.255.255.0


Are you sure this is correct ? I haven’t see default route (gateway).
Are you using ppp ?

Yes, I’m dialing into a PPP conection at my ISP.

From the setting above, I can’t even see how you could ping to the
DNS server (167.142.225.3).
Also, please note you must be “root” to run phlip…

I have been using root for most of this.

Another thing you could do is do a:

getconf CS_RESOLVE

cat /proc/ipstats

and post the output.

\

getconf CS_RESOLVE

nameserver_167.142.225.3
nameserver_167.142.225.5

cat /proc/ipstats

Ttcpip Jun 15 2000 22:36:01

verbosity level 0
ip checksum errors: 0
udp checksum errors: 0
tcp checksum errors: 0

packets sent: 5
packets received: 9

ppp0 : addr 199.120.118.183 netmask 255.255.255.0 up
en0 : addr 192.168.0.31 netmask 255.255.255.0 up
lo0 : addr 127.0.0.1 netmask 255.0.0.0 up

DST: 167.142.174.236 NETMASK: 255.255.255.255 GATEWAY: ppp0
DST: 192.168.0.0 NETMASK: 255.255.255.0 GATEWAY: en0
DST: 127.0.0.0 NETMASK: 255.0.0.0 GATEWAY: lo0
DST: 0.0.0.0 NETMASK: 0.0.0.0 GATEWAY: 167.142.174.236

<<<

I did the above while I was dialed into my ISP.

-xtang