LinHES Forums
http://forum.linhes.org/

access schedules direct problem - [Solved]
http://forum.linhes.org/viewtopic.php?f=21&t=21633		 Page 1 of 1
Author:  snaproll [ Thu Sep 23, 2010 1:34 pm ]
Post subject:  access schedules direct problem - [Solved]
I changed over my internet feed from DSL to Cable... thought my Mythboxes made the change OK, but it turned out two of them were reporting 'mythfilldatabase' ran OK, but no data is grabbed and the 'days of data' is running down hill.

I changed to the new DNS server shown in my router in the LinHes 'network' setup page, and can ping it from the non-cooperating Mythboxs, but I am getting 'unable to resolve 'webservices.schedulesdirect.tmsdatadirect.com' from mythfilldatabase.

The problem boxes talk to the internal network and mythweb just fine.

Three other Mythboxes on my internal network can access mythfilldatabase data just fine... The new cable connection gets it into the house...

Weather Data works on the 'good' machines. Not on the problem machines..

I tried to find differences between the working and non-working machines, but so far, no luck..

Netcardconfig is not available on 6 ?

Anybody spot what I'm overlooking ?
Author:  slowtolearn [ Thu Sep 23, 2010 3:07 pm ]
Post subject: 
If LinHes uses /etc/resolv.conf I would start there. Check the nameservers listed and compare with one of your working systems, I'm guessing you'll spot the difference(s).
Author:  mattbatt [ Thu Sep 23, 2010 8:11 pm ]
Post subject: 
you said you can ping SD correct? i noticed that the error says datadirect we havent used dd in years is the error code old or what version of KM or LinHES are you running on those boxes.
Did i read corrrectly that you have a box set up as a router? try plugging the comps directly onto the cable modem.
Author:  snaproll [ Fri Sep 24, 2010 6:16 am ]
Post subject: 
slowtolearn wrote:
If LinHes uses /etc/resolv.conf I would start there. Check the nameservers listed and compare with one of your working systems, I'm guessing you'll spot the difference(s).


Yep ! That solved it. (Amazing what the knowledge to know where to look can do ! )

The file in the problem machines contained 192.168.1.1 (The gateway for my internal network.)
I changed it to 68.94.156.1 (what was in the file for the successful machines..) and they started working, ( filldatabase and weather..)

Dunno if the gateway ip was working with the DSL setup, or how this file gets written, or where the working ip comes from (cuz it's not the primary DNS that I entered in the LinHes network setup page.) I suppose this is an automagic feature that usually goes unseen by us users, until circumstances manage to frustrate it.... :lol:

Since these were 'production' machines (messed with only when really necessary..) I appreciate you saving my WAF... Thank You !.... :D
Author:  snaproll [ Fri Sep 24, 2010 6:33 am ]
Post subject: 
mattbatt wrote:
you said you can ping SD correct?

I ssh'ed into the boxes and pinged my primary DNS for the cable system, it showed that the boxes could reach the outside world.


Quote:
i noticed that the error says datadirect we havent used dd in years is the error code old or what version of KM or LinHES are you running on those boxes.


They are 6.2 boxes, and the 'resolving' message is what was being returned. Perhaps they long ago named this file and can't change it now without messing up all the boxes that are out there ?


Quote:
Did i read corrrectly that you have a box set up as a router?

No. internet comes in on cable to a wired and wireless firewall router. The Mythboxes are on the wired side, one is two switches down from the router, the other is three switches down from the router, so...

Quote:
try plugging the comps directly onto the cable modem.

...I did try this in case it was a problem of getting through the switches, it wasn't.. as noted above, it was the ip in the /etc/resolv.conf file..... :D
Author:  slowtolearn [ Fri Sep 24, 2010 3:13 pm ]
Post subject: 
snaproll wrote:
Since these were 'production' machines (messed with only when really necessary..) I appreciate you saving my WAF... Thank You !.... :D
No problem. The gateway address may be due to a network manager (NetworkManager, dhcpclient, etc.) overwriting your resolv.conf file, keep this in mind after your next reboot. It can be maddening, so much so that I disabled any such "Network Manager" on my *nix systems.
Author:  snaproll [ Fri Sep 24, 2010 4:37 pm ]
Post subject: 
slowtolearn wrote:
snaproll wrote:
Since these were 'production' machines (messed with only when really necessary..) I appreciate you saving my WAF... Thank You !.... :D
No problem. The gateway address may be due to a network manager (NetworkManager, dhcpclient, etc.) overwriting your resolv.conf file, keep this in mind after your next reboot. It can be maddening, so much so that I disabled any such "Network Manager" on my *nix systems.

OK - So noted... I have bookmarked this thread for my 'obscure problems' manual :lol:

I further noted that the internet ip from the working machines was the old DNS for the DSL line, but it worked anyway... I changed them all to my current DNS and they still work, so I'm up to date. :D
Author:  mattbatt [ Sat Sep 25, 2010 12:12 am ]
Post subject: 
Awesome!! glad someone knew what they were talking about (it's very rarely me)
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/