Dear Comrads in Arms,
Since STN has been such a great success for me and my clients, I've decided it's
about time to broaden my Linux knowledge. So, I've install Caldera Linux on an
older Compaq P166/32MB Ram/3.0GB drive.
The Install went fine, but I've got some questions. And some of these are STN
related.
First, hostname is LinuxASB and under COAS under KDE (where one sets up
Network/Ethernet) the default was originally an IP of 198.162.1.1 with
Broadcast defaulted at 198.162.1.255 and subnet of 255.255.255.0. - and I got
out to the net through STN just fine with Netscape Linux.
But I was having trouble with SAMBA and my Windows clients. So, I changed the
IP to 192.168.0.2 (broadcast 192.168.0.255 and subnet 255.255.255.0 (to stay in
the same ring)). Again STN worked fine but trouble with Windows clients seeing
LinuxASB persisted.
I checked the ARP table on STN through browser login and didn't see the
192.168.0.2. In fact at first couldn't see how the LinuxASB box was getting
out. The only IP's showing were my known Windows boxes (either pre assigned
IP's by me or the DNS assigned by STN). And I couldn't ping 192.168.0.2 - so
what was assigned by STN?
So, I changed LinuxASB box to DHCP. STN assigned 192.168.0.105 and I saw it in
the ARP and was able to ping it. That worked but I really wanted an assigned
IP so, added 192.168.0.2 for Host LinuxASB to DNS tab on STN and remade
diskette and rebooted STN. Lo and behold, I still can't ping 192.168.0.2 (no
response). Yet smbclient -L LinuxASB returns 192.168.0.105 and the ARP of STN
shows this as assigned. (and I know it's assigned to LinuxASB). Why can't I
assign the IP to LinuxASB and get STN to accept it and not assign it's own
number? And some of the other Linux command ifconfig and nblookup confirm this.
In all of the above cases, I get out on the net through STN.
Finally, any suggestions on this: I've resolved samba so that smbclient -L
LinuxASB works correctly now and I'm in my correct Windows Workgroup and I can
login on LinuxASB computer to samba and get to the samba prompt and display
files/folders. I can even see LinuxASB with nbtstat -A 192.168.0.105 from a DOS
prompt on my Win98 and Win95 workstations displaying LinuxASB unique and the
correct workgroup as group. BUT, I can't see LinuxASB in network neighborhood
nor can I login to or attach to the Linux box while attemptin "net use t:
\\LinuxASB\tmp" or "net use t: \\192.168.0.105\tmp". I get the message "Error
51: The specified computer is not receiving requests. Make sure you are
specifying the computer name correctly, or try again later when the remote
computer is available." When I looked that up on the net, it was suggested that
I be sure that the tcp wrapper (???) was installed and that the hostname be
added to the host.allow file (but this file was empty and I'm not sure of the
format, maybe, just name or like lmhosts?). Also to get things working, I
needed to add "host deny = all" to smb.conf as suggested. Why would one add
deny = all, wouldn't that deny access? It went further to say that on the
Client Win boxes to add DSN server address and host name. I added domain
LinuxASB and added IP of 192.168.0.2 but didn't get anywhere.
I am running ipx and the nwlogin works fine with my Netware 5.0 server.
Although, as expected, no login script runs, but the NDS and bindery info
(including volumes) appear under folder NetWare.
So, how do I get my Win9x boxes the see the Linux workstation?
And, how do I get STN to let me have and use 192.168.0.2?
Any help/suggestions would be wildly appreciated.
Thanks,
Arnie
[EMAIL PROTECTED]
--
Visit http://www.ShareTheNet.com for info about ShareTheNet
Visit http://www.topica.com/lists/sharethenet for info about this list
_____________________________________________________________
Who will win the Oscars? Spout off on our Entertainment list!
http://www.topica.com/lists/showbiztalk
