Linux not seen from a Windows Ping?

[bcsmith100]

This is a new post on a problem I reported earlier. I have continued to work on the problem and now have a better handle on what (I think) the problem is.

I have been working on setting up a network of combined Linux and windows machines. On the Linux side I have setup Samba and Linux is able to see and access the Windows systems.

My problem is setting up access of my linux workstation from my windows machines.

I have Linux setup at an IP address and alias, I have went to the NetGear router and verified the Linux alias and address and from my windows machines I can ping the Linux via the ip address... BUT NOT THE ALIAS!!!!

This is where I am stuck. For the longest time, I had the Linux box setup with a hostname, but no alias...I gave it an alias now I have a hostname (dhcppc3) and an alias (linuxstation). The router can see the machine via the alias (linuxstation) and I am able to run services on the linux workstation via a URL based on the alias (i.e. linuxstation:8080).

So what could be wrong with my setup that allows the windows machines to see the IP address of my linux workstation, but not be able to ping via the alias know to the router?

I will keep working on this and report any progress I make, but suggestions would be appreciated.

[Bokkenka]

So what could be wrong with my setup that allows the windows machines to see the IP address of my linux workstation, but not be able to ping via the alias know to the router?

There's nothing to resolve the name. If you don't have a DNS listing, you can't surf the web because your www.name.com can't get resolved to the server's IP. Just set up a small HOSTS file in your c:\windows\ directory. It should look like...
# Copyright (c) 1998 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP stack for Windows98
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost

192.168.210.1 auroraborealis ab
192.168.210.11 daisho
192.168.210.12 wakizashi waki
192.168.210.13 ipaq
192.168.210.14 charlie


There should be a HOSTS.SAM that's a sample file. Save it with no extension... Just "HOSTS". You can put several aliases per computer per line.

[BrayA]

Just set up a small HOSTS file in your c:\windows\ directory.
I'm not sure about placement of this file over different versions of windows, but you may want to do a search in your windows folder and subdirectories for hosts*.*

On my win2000 box it was in C:\WINNT\system32\drivers\etc

But yes, Bokkenka I think nailed your problem.

[bcsmith100]

This worked. To be honest I thought you guys were wrong at first. I had figured out that if I shut off IPTABLES and IPCHAINS on the linux workstation that I could ping (and access via webpages) the Linux workstation. However, this method had problems with samba not giving me problems with accessing the workgroup on my windows PC.

So I tried to modify the host file in /windows/... directory as you guys suggested and this works as well....

Also, using this method I can still see the SAMBA directory from Windows.... When I try to access the SAMBA directory I get \\Linuxstation is not accessible. I figure that this is most likely a problem with either the way I have Samba setup or a Samba security problem. I have user security set for samba, and I have created a user for my windows PC, but I figure this has to be the source of the problem.

But anyway, I have figure out the base problem with your help. thanks!

[BrayA]

Anytime, good luck with that.

[Bokkenka]

When I try to access the SAMBA directory I get \\Linuxstation is not accessible.

Post your smb.conf, and we'll take a look.

In the mean time, did you "smbpasswd -a username" the accout you set up on the Linux box? This will create a listing in the Samba password file.

[grnfvr]

You guys seemed to be able to identify the hosts file very quickly. I am having the same difficulty, but i did not want to use hosts files as they are static. instead i just wanted to rely on netbios brodcasts for name resloution. I know netbios will not traverse subnets, but thats ok. im only dealing with a few hosts in one subnet. likewise i dont want to set up dns or wins for so few hosts. is there a way to get samba using netbios broadcasts (both in queries from windows hosts to the linux box and vice versa)? I cant seem to get it working....

Matt