Slackware :: Cannot Ssh Using Hostname, But Can Using Ip Address?
May 11, 2010
I have a machine running Slackware 13. Recently I had to modify network settings on it and now I cannot ssh into that box from my local LAN using machine's name. I can only ssh by using its IP address.I searched the forums, Google, but I cannot find the solution.
This morning it would not boot; when I tried to wake up the system, it gave me a bunch of errors, the last ones being as follows: "mount error: could not resolve address for servername: No address associated with hostname mountall: mount /media/shares [1402] terminated with status 1" I am writing this in Win 7 since I lost ubuntu. I am using ubuntu 11.04.
ok so when i sudo apt-get update i get a bunch of crap that says no address associated with hostname
ive googled this and changed my /etc/hosts to all sorts of things and no luck apache wont even work now either. this server is for a few websites the company i work for hosts. currently i swaped it over to another windows based comp but we want it on ubuntu.
ive heard this is dns related? and that a FQDN is needed? if so im not sure how to re write my /hosts file but as of not it looks like this:
Code: 127.0.0.1localhost 63.119.120.135speed # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback
Right now my setup is as follows: I have an Asus Eeepc 900 running Netbook Remix named eeepc, and a media centre running 64-bit Ubuntu named media.When I try to ping or ssh into one machine from the other, for exampleCode:$ ping mediaI get an "unknown host name" error. However, pinging the device's IP address works. How do I get the computers to recognize each other's host names? Did I miss something in the setup?
I have a ubuntu server 10.04 that will not boot. I saysno ip address specified and hostname not found refer to mount cifs blah blah blahmountall mount /directory/share [863] terminate with status 32I know its because I had a share mounted at boot but the server cannot mount the share for some reason. is there a way around this so I can boot the machine.I can ping the server. I just cant ssh to it. I need to get to a prompt some how so I can remove the mount from fstab.
I have a linux server running slackware 13.37. I am trying to mount a samba share with my other slackware machine, but I get a "mount error(13): Permission denied" when I run
sudo mount -t cifs //server/share /mnt But, if I run sudo mount -t cifs //192.168.1.100/share /mnt
New CentOS 5.4 system working fine. Sys admins came in and copied the hosts file from one of the servers down to my desktop and ever sincethen machine has been slow (progs take 10-20seconds to load). RunningGnome. Luckily I saved the old hosts file and copied it back and all is now well. But I'd like to understand why, particularly as I will need to change myhostname in the future.
As configured: /etc/hosts (yes my hostname is "dummyName" that I will need to change later) 127.0.0.1 dummyName localhost.localdomain localhost
I can reach other hosts by means of their global addresses by either the IP address or hostname (that has the global address). What I want to (also) do is have a hostname that references the IPv6 link local IP address (an AAAA record in DNS, or just the fe80::<whatever> address in /etc/hosts) and use that host name in commands to access that host. The problem is, an interface ID is needed when making such a reference.
It sure looks like the programs just pass the host name string on to the resolver library, which does not understand the significance of the '%' even though it could find and see that the name preceding the '%' is consistent with that being an IPv6 link local address (e.g. the logic could have been "split at first % and see if preceeding name is found as a link local address and accept that if so, or ignore the split otherwise" ... but it isn't). Is there a different syntax for this ... or was it overlooked in the design of programming around IPv6?I want to be able to address a host by its link local address, while still using a mnemonic instead of having to type the IPv6 address.
I have a version of slackware installed as a virtual machine and am not able to ping hosts or otherwise receive data from any IP addresses external to the LAN. I think this problem is due to the hostname of the vm not being recognized by the gateway (ddwrt); the vm receives an IP via dhcp but the gateway does not seem to recognize its hostname (registers as *).
Will readily respond with whatever conf file is needed.
I've setup two slackware in a Dell Inspiron 640m e in Acer Aspire One D150.
In my router the domain is "home", the two slack use wicd (dhcpcd backend) to connect. I can go in internet.
The problem is that in my router panel I can see the hostname (so dhcpcd send the right one) but they can't ping other machine in the lan (windows 2000, nas or other linux box).
Now I can't use a fixed ip (i change several networks with different routers).
I think I miss something that can ask to my router the hostname.
Anyway I was able to ping Dell.local and Acer.local with Ubuntu karmic.
I used to configure hostname in the rc.inet1.conf, DHCP_HOSTNAME[0] option and the router was able to recognize the client name, but with Slackware 13 it seems that there is a configuration I'm missing.
I am having a problem logging into my remote gentoo (2.6.23) linux machine using my hostname from my Windows XP machine using cygwin. I can login using my ip address, but not the hostname.
This works: $ ssh me@xxx.xxx.xx.xxx
This does NOT work: $ ssh me@my_hostname ssh: connect to host my_hostname port 22: Connection refused
I have verified that my hostname is indeed "my_hostname" on my linux machine by using the "hostname" command.
During Slackware 13.1 setup, I chose the hostname stella-sl2. This hostname is also the one that the system is displaying before I configured network access. After configuring wired network access to my Apple Time Capsule, my hostname suddenly changed to INTERFACE='eth0'. As a result I'm noticing some very strange things, like the login prompt which has become "INTERFACE='eth0' login: ".
After configuring wireless network access to the Time Capsule, the hostname changed to "INTERFACE='wlan0'". Note that, during boot, wlan0 is brought up AFTER eth0.
Until now, it was only a minor annoyance, it didn't prevent anything from happening, internet connection was not affected. But now I'm configuring sendmail which needs to talk to a relay SMTP server, and sendmail "HELO"'s itself using the bogus hostname:
Probably this is caused by the Time Capsule not adhering to standards. However, the Time Capsule's firmware is the latest version, so I cannot fix this. Is there a way to prevent dhcp from changing the hostname? How can I make sure that the hostname that I configured during setup remains active?
I have a network of 2 WinXP machines and one linux box. I have fiddled around with the settings as you do when learning. The network is working. The network neighbourhood on the WinXP machines recognise the linux box and vice versa, (the linux Places|Network recognises the 2 WinXP). I can Ping the linux box using its hostname from a WinXp. But I cannot do the reverse. I get an 'unknown host' response. I can ping the linux to itself using its hostname.
I'm having an issue on two Fedora Core 13 machines where I can ping others by hostname, but the hostname resolution fails whenever I use ssh/scp/vnc/etc. I can still do these things by IP address, just not by hostname. RHEL5.3 machines on the same network with the same configuration do not seem to have this problem.
Here's the not-so-quick-and-dirty description of the situation:
I know that there is a virtual router at 192.168.31.1 and another at 192.168.30.1. I also know that there is another network (let's call it 90.90.90.0) and on that network lies a number of resources. By nature of this configuration, any machine on 90.90.90.0 can be accessed by any 192.168.x.x, but not the other way around. Beyond that is out of my hands and currently out of my scope of knowledge.
I have a dnsmasq server on 90.90.90.10 that operates as a secondary nameserver, another machine out of my sphere of influence is the primary nameserver (90.90.90.31).
The secondary nameserver on 90.90.90.10 holds the hostnames of our development machines. The problem is that in some cases, while I can ping by hostname all day long, services such as ssh, scp, vncviewer, etc all fail to resolve the hostname. In other cases I can do all of these things.
Every machine has an equivalent resolv.conf:
As an example, I will show the output of a handful of my development machines:
I also included columbia as a one-way test -- even though it cannot access 30.x or 31.x, they can access it:
columbia -- physical machine, Red Hat Enterprise 5.3, IP 192.168.100.200
Okay, so here are the various outputs. Remember, nibbler, discovery, and atlantis can ALL: - Ping by IP address - Ping by hostname - ssh, scp, vnc, etc by IP addess
Additionally, the SERVFAIL reply from 90.90.90.31 is expected since my dnsmasq server is on the secondary server.
Note that the only machine that can both ping and ssh/scp/etc by hostname is nibbler, which also happens to be the only one of the three running RHEL5.3 instead of FC13. Other virtual and physical machines running on the 192.168.31.0 and 192.168.30.0 networks (all running RHEL5.3) work just like nibbler does. So the problem seems to only affect machines running FC13.
Final note: selinux is disabled, iptables is disabled, ip6tables is disabled.
Other than that, discovery is a brand-spanking-new install straight off of the FC13 DVD. atlantis has been around longer, but its just a file server so I haven't done anything too crazy to it.
I'm trying to ping another Ubuntu computer on my local network. If I try doing,ping <hostname>then I get the messageping: unknown host <hostname>however, if I doping <hostname>.localthen I get a response back. I was wondering how I can change it so that I can ping without having to append .localI've installed winbind and modified my /etc/nsswitch.conf file but this has made no difference.
I have an ubuntu 10.04 server with hostname "abc.domain.com". However, due to migration, we had to change to hostname to something else, "xyz".
I have done changing /etc/hosts and /etc/hostname and run /etc/init.d/hostname start.
Checking the hostname and all shows it is now using hostsname of xyz. However, email sending out is still using old hostname. We have some scripts that will send out alerts like failed rsync or hdd space full to my email account. But I see the sender is still "root@abc.domain.com".
How do change that to xyz? I am using postfix. I have edited main.cf and restarted postfix but no go.
On Slackware 13.1, I am trying to connect to another computer using:
X :1.0 -query <hostname>
but I get a black screen and then the following error:
$ X :1.0 -query slackserver X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0
[code].....
I tried to connect to both another Slackware 13.1 computer and a Debian computer. I also edited the /etc/X11/xdm/Xaccess file on the remote host to enable the graphical login access. I always get the same error.
If I need to adjust my network settings (rc.inet1.conf) on the fly, like if I need to be in the local network of a router I just bought (192.168.1.x), in order to change the subnet to the rest of my network (192.168.0.x), then I need to adjust the ip address of my slackware box. Up till now I have rewritten the rc.inet.conf file and then restarted the computer. I am almost positive that restarting is unneccesary, but I have not been successful in finding any other method. Maybe I am using the tool wrong, but I have tried using wicd to disconnect and then connect again once I change the rc.inet1.conf. I don't think it worked. I think I have also tried issuing a rc.inet1 restart. But I don't think that this changed my ip address either. How do you change your ip address on the quick without restarting your box?
I have a slackware server running ISC dhcpd and bind, and I want to give a dual boot XP / Ubuntu client a fixed address based on its MAC.
I added a host stanza to my server's dhcpd.conf:
Code:
I restarted bind and dhcpd, restarted the client's networking, and it still requests (and receives) its previously leased address, which is not the fixed address I want it to get. I tried dhclient -r to make the client release the old address, didn't help. On networking restart it still gets offered the old (wrong) address. Could it be that dhcpd somehow hangs on to the old lease even after the client sent a DHCPRELEASE?
How do I tell dhcpd to forget about an old lease, and how do I make dhcpd hand out the fixed address (and only that address) I specified for a given MAC, regardless of what the client requests?
1) I'm not sure which IP address to use when I list my machine name in /etc/hosts, particularly after reading:
Quote:
By the w]ay, Arnt Gulbrandsen <agulbra@nvg.unit.no> says that 127.0.0.1 # should NEVER be named with the name of the machine. It causes problems # for some (stupid) programs, irc and reputedly talk. :^)
Here's what I have now: Code: root@eagleswing:~# hostname eagleswing root@eagleswing:~# cat /etc/HOSTNAME eagleswing.5binc
[Code]...
I'm not certain how to include my router in /etc/hosts so I can use it to link my PCs as stated above. I was thinking of writing (see above link):
192.168.2.1 localbelkin Will this work & is it proper?
3) Do I need to make use of any other IP addresses at this link? What are the WAN IP & Default Gateway addresses used for? I am going to be serving documents & running scripts on Apache.
My wife takes her laptop on her travels but recently has been getting a connection refused when attempting to connect to our home server. The only reason I believe this is occurring is because of iptables blocking certain IP addresses which I don't want to delete for SPAM prevention.
What configuration what be both secure and relatively straight forward. Initially configured mac filtering but then realised this would not be appropriate under these circumstances..
Also there is no specific logging in either postfix or dovecot about connection refused.
Slackware 10.2. My usb ports work fine when used directly. When I insert a USB hub to duplicate a port I get the message USB device not accepting new address=2 error=-71
I have currently installed Slackware 13.1 64bit version on a laptop Acer computer. This computer is connected to my cable service (comcast) modem via a dlink router. This computer has linux and Windows 7 dual boot systems installed. Initially I was able to connect to the internet with either linux or Windows. Now I cannot get on the internet with linux, but I can with windows.
I cannot even ping the address of my internet provider,which I can obtain through windows 7 by running the program ipconfig. When I ping the address, in linux,it gives me the message that "network is unreachable".I can ping it in windows 7.If I run on linux the program ifconfig, it does not even show an ethernet, like it does on my other computer connected to this network.I set the thing up initially with netconfig and used DHCP.As I said, initially it worked.I did not use this computer for some time, and now it has the previously described problems.Where should I start, trying to run this down?I have already done everything I can think of,like powered things off, and reset the cable modem etc.
If I have a dnsmasq server and it dished out a IP address that I don't want it to and it still gives it to my machine no matter how many times I restart windows and issue ipconfig /renew|release or enable/disable the adapter, how do I force it to give my windows machine an IP I want it to have?
The only way I've accomplished this in the past is by rebooting my slackware system.
I recently upgraded my motherboard which has a different onboard NIC chip than the old one. I donwloaded the NIC driver from the vendor's website and installed it. I tried setting up the new NIC with netconfig. The tool seems to run correctly, but the settings don't seem to do anything. I then tried setting up the interface by editing the info into /etc/rc.d/rc.inet1.confg. That works fine, but there is no place to specify the DNS server address. Where is the DNS address stored?