The name "localhost" has a special meaning in TCP/IP networking- it is an alias to the local loopback device IP of 127.0.0.1, which is present on any machine running TCP/IP regardless of operating system. As such, "localhost" should never be used as the actual computer name/hostname for any machine on a network, because it causes exactly the conflict you're experiencing.
If any computer on your network is using "localhost" as its hostname, you need to change that name to something unique.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
To set the machine's host name in Redhat, you can do one of two things:
A) In the /etc directory you might find a file named HOSTNAME (if you don't, just create the file). It should contain a single line containing the hostname.
B) In your /etc/sysconfig/network file, enter the hostname after the equal sign on the "HOSTNAME=" line.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
OK- try this:
Open your /etc/hosts file in a text editor and do the following:
Change the line that reads something similar to:
127.0.0.1 localhost.localdomain localhost
to:
127.0.0.1 localhost.localdomain localhost put_your_new_hostname_here
For example, if you chose a hostname of "linuxbox", the entry would read:
127.0.0.1 localhost.localdomain localhost linuxbox
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
Sorry- I should have asked this before: are you assigning your IP info to each of your machines manually, or do you have a device (a router perhaps) acting as a DHCP server for your network? Issues of hostname problems vary depending on which addressing scheme you use.
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
I fussed around with localhost network settings for a few hours and then just started the smb service and it worked.
And so you dug up a 1 1/2 year old thread just to let us know? :mrgreen:
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370
I got sidetracked because "localhost" was showing up in windows and I thought windows was compaining because it didn't like the name "localhost".
You're right- any computer (regardless of OS) running the TCP/IP protocol uses the local loopback IP address of 127.0.0.1, which is traditionally aliased to the name "localhost".
Given that, the net effect (no pun intended) of using "localhost" as a computer's network hostname can cause about the same amount of confusion as filling a room with a bunch of guys all named Bob Smith and then trying to do a roll call. I'm putting this here so that when I have this problem again, it might only take 15 minutes instead of 2 hours to fix it... :)lol- good future planning...
BTW- welcome to DaniWeb! :)
DMR
Wombat At Large
7,229 posts since Dec 2003
Reputation Points: 221
Solved Threads: 370