Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

resolv.conf

Status
Not open for further replies.

johny2K

Technical User
Dec 19, 2001
184
CA
i have 2 redhat 7.1 servers, basically same configurations - i am wondering how come i can't telnet the other one and each time i check /etc/resolv.conf - it changes for unknown reason. i used "setup" to configure each network (they are both on the same LAN). i verified /etc/xinetd.d/telnet - both are the same...

what must be wrong?

thanks.
 
Are both machines using static IP addresses? One of the things DHCP does is set the name servers -- and resolv.conf is changed to reflect the name server settings reported by the DHCP servers.



Want the best answers? Ask the best questions!

TANSTAAFL!!
 
In the file /etc/securetty, do you have
pts/0
pts/1
...
?

If not, edit this file and write them.

regards,

GBy
 
sleipnir214 - yes, they're both have static IPs as I set it up using the "setup" command and verified each time with "netstat -rn".

gui95 - i did, but for still unknown reason, something is changing the resolv.conf. Looks like it's not holding on to what I saved.

i can ping the default router, too. I can telnet to other server/s from this problematic server, but not vice-versa.

 
check the file:
/etc/sysconfig/network-scripts/ifcfg-ethN
where N=0 if device is eth0

regards,

Gby
 
Hello - what about it Gby?

here it is:

DEVICE=eth0
ONBOOT=yes
BOOTPROTO=static
IPADDR=192.168.45.15
NETMASK=255.255.255.0
GATEWAY=192.168.45.1
 
thanks...

i was able to find the culprit - it's the ipchains service that screwing things up.

i tried these:

1.) verified "/var/log/messages" and look for un-necessary or shall we say - unusual processes..

May 5 13:04:04 localhost ipchains: Flushing all current rules and user defined chains: succeeded
May 5 13:04:04 localhost ipchains: Clearing all current rules and user defined chains: succeeded
May 5 13:04:05 localhost ipchains: Applying ipchains firewall rules succeeded

2.) killed the process, by;

# service ipchains stop

***/var/log/messages shows;

May 5 13:18:01 dcs02 ipchains: Flushing all current rules and user defined chains: succeeded
May 5 13:18:01 dcs02 ipchains: Clearing all current rules and user defined chains: succeeded
May 5 13:18:01 dcs02 ipchains: Applying ipchains firewall rules succeeded
May 5 14:46:00 dcs02 ipchains: Flushing all chains: succeeded
May 5 14:46:00 dcs02 ipchains: Removing user defined chains: succeeded
May 5 14:46:00 dcs02 ipchains: Resetting built-in chains to the default ACCEPT policy succeeded

3.) checked right-after and found out - it is working... i was able to telnet the server from other server.

:D

 
[tt]
i was able to find the culprit - it's the ipchains service that screwing things up.

i tried these:

1.) verified "/var/log/messages" and look for un-necessary or shall we say - unusual processes..
...
2.) killed the process, by;
[/tt]

Usually when I'm "helping someone solve a network problem", the first thing I tell them to do is drop their firewall. That will make things better.

Seriously. I mean, what can be so bad on the internet. Everyone is friendly, right?
</sarcasm>
I'd rather suggest you should read the Linux IPCHAINS-HOWTO, and maybe this or that. Don't just throw down your defenses because you want to use *gag* telnet. *sigh* I need a beer. Been a long day ;-)

Check out those links, will try to help out later if you want it.

----
JBR
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top