Topic: 4.0 Ibay Issue

[Glenn Kennedy]

I'm running 4.0b (Feb 7), and posting this message from a client machine behind
the e-smith gateway. I have telnet and ftp access set to private, I have the
e-smith server set to the same workgroup as this win98 box. I created an Ibay
called "sales" and have set its group access to everyone and the "User access
via file sharing or user ftp" to write=group, read=everyone. Public access is set to
local network.

My problem is that I can't connect to the share in windows explorer, using
map network drive "\e-smithsales. I can, however, see the ibay from ftp.

The e-smith box doesn't show up in network neighbourhood from windows this
windows client either.

Comments?

Glenn Kennedy

[cryblood]

I've not played with e-smith 4 as of yet, but I have had a problem with an AIX UNIX box that sounds similar.  The fix for my problem was to add a line for the UNIX box in the hosts.sam file in the windows directory and rename it to hosts (without the .sam extention)  Remember to rename the file, winblows doesn't actually use it when it's named hosts.sam.

example hosts file:

#
# bla bla typical M$ mine mine mine all mine crap
#
127.0.0.1       localhost
192.168.0.1    unixBoxenName


I can't say for sure if this will help you, but for future reference to all, I find that this fixes a lot of M$  Wins  problems with UNIX connectivity in general.

[Charlie Brady]

cryblood wrote:

> I have had a
> problem with an AIX UNIX box that sounds similar.  The fix for
> my problem was to add a line for the UNIX box in the hosts.sam
> file in the windows directory and rename it to hosts (without
> the .sam extention)

...

> I can't say for sure if this will help you, but for future
> reference to all, I find that this fixes a lot of M$  Wins
> problems with UNIX connectivity in general.

If an addition to the lmhosts file, or even hosts file, fixes a Windows networking problem, it's a sure sign that Netbios name
resolution isn't working properly. The latest 4.0 beta has DHCP
setup correctly so that Windows clients can resolve names using WINS, as long as the clients are configured to use DHCP, and to
locate the WINS server using DHCP. These are both checkboxes under Control Panel->Network->TCP/IP->Properties.

Don't fiddle with hosts or lmhosts files on Windows boxes if you can avoid it. You'll be doing it forever.

If you continue to have trouble, find Diagnostics.txt under /usr/doc/samba-2.0.5a and go through it a step at a time.

Charlie

[Glenn Kennedy]

Thanks to both of you.

Charlie - I tried your suggestion first, that is checking
'Use DHCP for WINS resolution' from Win TCP/IP network menu. It still
didn't work, I thought I'd try selecting Enable WINS
resolution and specifying 192.168.1.1 as the WINS server. That worked.

Thanks again,

Glenn Kennedy

[Charlie Brady]

Glenn Kennedy wrote:

> Charlie - I tried your suggestion first, that is checking 'Use
> DHCP for WINS resolution' from Win TCP/IP network menu. It
> still didn't work, I thought I'd try selecting Enable WINS
> resolution and specifying 192.168.1.1 as the WINS server. That
> worked.

Hmm, that indicates a problem with DHCP configuration. Could you
please run "winipcfg" on your WIndows machine, click More Details, and email me a summary?  Let me know what e-smith-base RPM you have installed as well.

Thanks

Charlie