If this is how your file /etc/resolv.conf looks:
search ig.com.br
ig.com.br 200.225.159.124
ig.com.br 200.225.159.126
#itelefonica.com.br
#itelefonica.com.br 200.204.0.138
#itelefonica.com.br 200.204.0.10
then the error message is right.
What you need is:
search ig.com.br
nameserver ig.com.br 200.225.159.124
nameserver ig.com.br 200.225.159.126
#nameserver itelefonica.com.br
#nameserver ielefonica.com.br 200.204.0.138
#nameserver itelefonica.com.br 200.204.0.10
nameserver is of course ignored in the three lines starting with # but
better correct it NOW for the day you will want to use the other ISP.
And remember that the nameservers are tried in the order shown, again
for the day you may want to use the other ISP.
Marv had written to you that you need the word nameserver
If you have it and the same error persists, send us your
/etc/resolv.conf and your /etc/wvdial.conf AFTER ERASING THE PASSWORD in
a copy of /etc/wvdial.conf which you will send.
Jacques
Jose Fernando de Jesus wrote:
Marvin, I have done what you said but I still have the same problem. I had
already put the line 'Auto DNS = yes' into wvdial.conf before.
I still have the following last lines on the wvdial output:
--> warning, no nameserver found `/etc/resolv.conf`
--> Nameserver (DNS) failure, the connection may not work.
--> Connected... Press Ctrl-C to disconnect
If it's a problem with the Fedora release 7 or the kernel, I may be able to
upgrade to Fedora 8 until the end of the month. Also, I was also thinking
about to change to Mandrake 10.0, as it is supported by Motorola. Is this a
reliable distribution?
Thank you.
On Mon, 5 May 2008 21:15:00 -0400, Marvin Stodolsky wrote
Jose
to /etc/ppp/options
add a line
usepeerdns
To /etc/wvdial.conf
add a line
Auto DNS = yes
MarvS
On 5/5/08, Jose Fernando de Jesus <jfernando@xxxxxxxxxxxxxxxx> wrote:
Antonio,
I have tried with both servers, itelefonica and ig and I had always the
same problem, which is shown on the output of wvdial below. It says about
DNS
failure, take a look:
[jfernando@bunitinhu ungrab-winmodem-20070505]$ sudo wvdial
--> WvDial: Internet dialer version 1.54.0
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT33550317
--> Waiting for carrier.
ATDT33550317
CONNECT 45333
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Mon May 5 18:42:48 2008
--> pid of pppd: 3347
--> Using interface ppp0
--> Authentication (PAP) started
--> Authentication (PAP) successful
--> local IP address 200.226.182.160
--> remote IP address 201.28.132.126
--> primary DNS address 200.225.159.124
--> secondary DNS address 200.225.159.126
--> Script /etc/ppp/ip-up run successful
--> Default route Ok.
--> warning, no nameserver found `/etc/resolv.conf`
--> Nameserver (DNS) failure, the connection may not work.
--> Connected... Press Ctrl-C to disconnect
On /etc/resolv.conf, I had put the following lines, with the '#'
indicating
the itelefonica options:
search ig.com.br
ig.com.br 200.225.159.124
ig.com.br 200.225.159.126
#itelefonica.com.br
#itelefonica.com.br 200.204.0.138
#itelefonica.com.br 200.204.0.10
Any suggestion is welcome. Thank you.
On Mon, 5 May 2008 23:39:57 +0000, Antonio Olivares wrote
Jose,
I took a look into the page
http://itelefonica.terra.com.br/ajuda/discador_a.htm
and looks like the ISP works more with windows
O discador é compatível com todos os sistemas operacionais?
Não. O discador é compatível somente com Windows 95, 98, ME, NT,
2000 e XP.
Translation.
Is this service compatible with other operative systems?
No, It is designed and compatible with only Windows 95, 98, ME, NT,
2000 e XP.
However, do not let this discourage you. Marv, Jacques and others on
this list are very capable and can share with you as how go about it
and get connected with linux.
Regards,
Antonio
On 5/5/08, Antonio Olivares <olivares14031@xxxxxxxxx> wrote:
Jose,
Use the numbers and add a corresponding nameserver on
them so that /etc/resolv.conf looks like
# cat /etc/resolv.conf
search example.net
nameserver 200.204.0.138
nameserver 200.204.0.10
This should get you connected, if this does not
happen, Carefully read Jacques' post-install
troubleshooting guide
http://linmodems.technion.ac.il/post-install.html
Regards,
Antonio
--- Jose Fernando de Jesus
<jfernando@xxxxxxxxxxxxxxxx> wrote:
Antonio,
I have followed all the steps you told me but I'm
not still able to browse.
The Network Manager is off. I did the eth0 down.
About the file resolv.conf I
have the following doubts: the output I have from
wvdial is:
[root@bunitinhu ~]# wvdial
--> [root@bunitinhu ~]# wvdial
--> WvDial: Internet dialer version 1.54.0
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT30095515
--> Waiting for carrier.
ATDT30095515
CONNECT 46667
--> Carrier detected. Waiting for prompt.
UQKT2 78.1
Login:
--> Looks like a login prompt.
--> Sending: jfernando1980@xxxxxxxxxxxxxxxxxx
jfernando1980@xxxxxxxxxxxxxxxxxx
Password:
--> Looks like a password prompt.
--> Sending: (password)
Entering PPP Session.
IP address is 201.93.49.96
MTU is 1100.
--> Looks like a welcome message.
--> Starting pppd at Mon May 5 15:42:43 2008
--> pid of pppd: 3323
--> Using interface ppp0
--> local IP address 201.93.49.96
--> remote IP address 200.100.131.77
--> primary DNS address 200.204.0.138
--> secondary DNS address 200.204.0.10
WvDial: Internet dialer version 1.54.0
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT30095515
--> Waiting for carrier.
ATDT30095515
CONNECT 46667
--> Carrier detected. Waiting for prompt.
UQKT2 78.1
Login:
--> Looks like a login prompt.
--> Sending: jfernando1980@xxxxxxxxxxxxxxxxxx
jfernando1980@xxxxxxxxxxxxxxxxxx
Password:
--> Looks like a password prompt.
--> Sending: (password)
Entering PPP Session.
IP address is 201.93.49.96
MTU is 1100.
--> Looks like a welcome message.
--> Starting pppd at Mon May 5 15:42:43 2008
--> pid of pppd: 3323
--> Using interface ppp0
--> local IP address 201.93.49.96
--> remote IP address 200.100.131.77
--> primary DNS address 200.204.0.138
--> secondary DNS address 200.204.0.10
Is these 2 last numbers that I have to put on the
/etc/resolv.conf file? Is
the name server the name of the server I want to
connect to? Should it be
given the complete server name, with dots?
I have already tried all of it, but I'm still not
able to browse. Either I
did not understand this step or the nameserver I
have is wrong. I have tried
itelefonica.com.br, which is the last part of my
dialer login.
Thank you.
On Mon, 5 May 2008 05:03:20 -0700 (PDT), Antonio
Olivares wrote
Jose,
Check to see if NetworkManager and NetworkManager
dispatcher are running
# chkconfig NetworkManager --list
if they are on, turn them off by doing a
# service NetworkManager off
and turn it off from starting completely do a
# chkconfig NetworkManager off
then look for your settings ie, which DNS(Domain
Name Servers) you
need for your ISP, and put them into your
/etc/resolv.conf an
example would be
cat /etc/resolv.conf
nameserver 19.190.128.1
nameserver 19.195.128.1
Also turn off eth0 connection by doing a
# ifconfig eth0 down
then try to connect again.
HTH,
Antonio
----- Original Message ----
From: Jose Fernando de Jesus
<jfernando@xxxxxxxxxxxxxxxx>
To: Antonio Olivares <olivares14031@xxxxxxxxx>
Sent: Sunday, May 4, 2008 9:02:17 PM
Subject: Re: Fernando, Brazil Fedora release 7
(Moonshine) Kernel
kernel 2.6.21-1.3194.fc7
Hi, finally I was able to connect using the
scripts you sent me,
but I was not able to browse. Is there any
settings I have to
provide to Firefox? What should I do?
Thanks a lot.
On Sun, 4 May 2008 17:27:37 -0700 (PDT), Antonio
Olivares wrote
Jose,
for a working example you may look here for
automation
http://www20.brinkster.com/olivares/slmodemd-setup-1.html
I did not update it for Fedora 7/8 but it works
the
same, you can add the line that Marv told you to
/etc/modprobe.conf as su -(Super User), then
also # cp
slmodem-2.9.11-20080417/scripts/slmodemd
/etc/rc.d/init.d/
# cd /etc/rc.d/init.d/
[root@localhost init.d]# chmod +x slmodemd
[root@localhost init.d]# chkconfig slmodemd
--add
[root@localhost init.d]# chkconfig slmodemd on
Should take care of it. You might need the
lines
modprobe ungrab-winmodem
modprobe slamr
in start procedure in the case that upon startup
you
see ``slmodemd dead but subsys locked'' message
start() {
modprobe ungrab-winmodem
modprobe slamr
echo -n "Starting SmartLink Modem driver
for
$SLMODEMD_DEVICE: "
$prog /dev/null 2>/dev/null \
--country=$SLMODEMD_COUNTRY
$SLMODEMD_OPTS
/dev/$SLMODEMD_DEVICE &
RETVAL=$?
[ $RETVAL -eq 0 ] && success $"$prog
startup"
|| failure $"$prog startup"
echo
[ $RETVAL -eq 0 ] && touch
/var/lock/subsys/$prog
return $RETVAL
}
Regards,
Antonio
--- Marvin Stodolsky
<marvin.stodolsky@xxxxxxxxx>
=== message truncated ===
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
José Fernando de Jesus
Physics Graduated
PhD Student on Cosmology (IAG-USP)
Rua do Matão 1226
Cidade Universitária
05508-900 São Paulo SP
Brasil
Phone: 55 11 30912732
email: jfernando@xxxxxxxxxxxxxxxx
(:¿(c)2007(c)?:)
Rock'n'Roll!
José Fernando de Jesus
Physics Graduated
PhD Student on Cosmology (IAG-USP)
Rua do Matão 1226
Cidade Universitária
05508-900 São Paulo SP
Brasil
Phone: 55 11 30912732
email: jfernando@xxxxxxxxxxxxxxxx
(:¿©2007©?:)
Rock'n'Roll!
