| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 41303 | 2004-01-06 07:37:00 | RedHat 9 dod | JohnD (509) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 205688 | 2004-01-06 07:37:00 | As I have mentioned in some previous posts over the last few years, I look after a Linux Samba server and gateway at a school in my spare time (for professional development mainly!). It is currently running RH7.0 and I am in the process of upgrading to RH9. I am doing this non-destructively (because it is holiday time!) by doing the RH9 install on a new HDD. If I don't get there - I can always easily revert to RH7.0. I am having trouble getting the dial on demand to go in RH9. In RH7.0 my method is: 1. copy your /etc/ppp/peers/wvdial file to a new file called dod. 2. Modify the file to look like: ~~~~~~~~~~~~~~~~~~~~~~~~~~~ noauth name wvdial connect "/usr/bin/wvdial --chat xtra" /dev/ttyS0 115200 modem crtscts defaultroute usehostname user [username added in here] noipdefault idle 180 persist demand logfd 6 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3. Add "pppd call dod" to the /etc/rc.d/rc.local file to make the demand dialling active. I will eventually set up a decent firewall but at the moment I have iptables running and the 3 lines: modprob iptable_nat iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE echo 1 > /proc/sys/net/ipv4/ip_forward added to the end of my /etc/rc.local file. The above general method works well with RH7.0. With RH9 when you load (say) IE at one of the Windows workstations on the LAN, dial on demand happens but no connection is made. In the /var/log/messages file I get this message: tdb_store failed: corrupt database or tdb_store failed: IO error. I have searched the net for what this means but have not found much sense. Two other points of interest 1. I can make a connection to the net with the RH9 server using kppp fine. 2. Once I have made a connection using kppp, I can surf the net from a Windows workstation. ....But no connection using dod. Any ideas would be appreciated. JohnD |
JohnD (509) | ||
| 205689 | 2004-01-06 08:07:00 | Very strange. Might you have bad sectors on the disk? | Dolby Digital (160) | ||
| 205690 | 2004-01-06 08:40:00 | It's a brand new Seagate 40G drive. | JohnD (509) | ||
| 205691 | 2004-01-07 01:48:00 | I see what you mean about the Google links for that error message. I had an idea that this would be a Samba problem, so a bit of digging has given me a couple of ideas. What version of Samba are you running? I see that version 2.2.1 fixed a "tdb corruption problem in connections.tdb" . ;-) It also moved the connections.tdb file to /var/run/samba/ from its previous location at /var/lock/samba/ (because RH clears the /var/lock tree at boot time --- a non existent file can be "corrupted" if it's a database file.) Try a locate connections.tdb and see where the file is. I think a change to the latest Samba release will help. (save copies the configuration files for the current version to make things easier if there are changes in configurartion between the versions). |
Graham L (2) | ||
| 205692 | 2004-01-07 07:30:00 | From my home version of RH9: 1 . Version of Samba = 2 . 2 . 7a . 7 . 9 . 0 2 . Location of the connections . tdb file = /var/cache/samba But thanks Graham - you have started me thinking . I wonder if my quick and dirty way of getting Samba up and running is the culprit - (I just copied the RH7 . 0 samba . conf file to RH9 and all seemed to work so I just proceeded) . So what I will try first is to create a new RH9 version of samba . conf from scratch and see if that is the problem . . . . . . but why is samba causing dod not to work? John |
JohnD (509) | ||
| 205693 | 2004-01-07 21:21:00 | 1. Have updated to the latest smb.conf file and restarted Samba - no change. 2. Have shut Samba services down - no change. Wouldn't that show it has nothing to do with Samba? |
JohnD (509) | ||
| 205694 | 2004-01-07 22:34:00 | I'm not that familiar with kppp, but I wonder if it writes some work files in the background that you could intercept and see how its connecting.... just an idea. | Dolby Digital (160) | ||
| 205695 | 2004-01-07 22:46:00 | I have reinstalled ppp. No change. When from the command prompt I issue the command "wvdial xtra" I get pppd error 19 which means that I am unable to authenticate - this is frustrating because the wvdial.conf file has the same username and password as kppp does!! (... and I am on line at the moment at the server using kppp). Still getting the 1. tdb_store failed: IO Error 2. tdb_store key failed: IO Error in the /var/log/messages file |
JohnD (509) | ||
| 205696 | 2004-01-09 07:52:00 | Found another slightly different method at: listman.redhat.com When I got to the part that says to test with: /usr/sbin/pppd /dev/ttyS0 115200 user yourusernamegoesinhere connect "/usr/sbin/chat -v '' AT OK ATDT08450885056 CONNECT '\d\c' " I again got the message: tdb_store failed: IO Error Went home and tried the same on my RedHat system installed from the same original CDs and got no error. Looks like a reinstall might be the next thing to do. John |
JohnD (509) | ||
| 205697 | 2004-01-12 07:09:00 | I have spent hours on this problem to no avail - until I decided to format and re-install and reconfigure from scratch. .... and it works beautifully!! There was no install errors on the first go but obviously something was wrong. So in case someone is following this thread - the dial on demand configuration above is valid. |
JohnD (509) | ||
| 1 | |||||