All -
I got several responses regarding the situation in my previous
email (included below). I now have the following setup and still get
nothing. I am able to see other entries in the Network Neighborhood, I am
just unable to logon to my samba server, or see it in the Network
Neighborhood.
W95 client on subnet 172.20.151.0/255.255.0.0.
- NetBEUI: "Client for MS Networks" is unchecked under Bindings tab.
- IPX/SPX: "I want to enable NetBIOS over IPX/SPX" is unchecked under
NetBIOS tab. "Client for MS Networks" is unchecked, but "Client
for Netware Networks" is checked under Bindings tab.
- TCP/IP is setup to use a WINS server (same as samba), but after it the
client reboots, WINS is disabled. Any ideas why?
- windows\lmhosts contains: "209.67.71.165 sos #PRE". I've tried
adding
"#DOM:sos" as well and get nothing different.
samba server is Solaris 2.6, samba version 1.9.18p4. My smb.conf looks
like:
---------------------------------------------------------------------------
[global]
workgroup = SOS
security = user
interfaces = 209.67.71.165/255.255.255.240
bind interfaces only = yes
allow hosts = 172.20.151. , 207.82.195., 209.67.71.160/255.255.255.240
domain logons = yes
logon script = logon_script.bat
domain master = yes
local master = yes
preferred master = yes
os level = 65
netbios name = SOS
wins support = yes
client code page = 437
preserve case = yes
short preserve case = yes
#create mask = 0000
#force create mode = 0644
invalid users = root
locking = yes
strict locking = no
name resolve order = hosts lmhosts wins bcast
veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
[homes]
available = yes
browseable = no
guest ok = no
writable = yes
---------------------------------------------------------------------------
Upon startup log.nmb reports:
---------------------------------------------------------------------------
05/14/1998 16:30:43 netbios nameserver version 1.9.18p4 started
Copyright Andrew Tridgell 1994-1997
register_name_response: server at IP 209.67.71.165 rejected our name
registration of SOS<00> with error code 5.
fail_register: Failed to register name SOS<00> on subnet UNICAST_SUBNET.
standard_fail_register: Failed to register/refresh name SOS<00> on subnet
UNICAST_SUBNET
add_domain_logon_names: At time 05/14/1998 16:30:44 attempting to become
logon server for workgroup SOS on subnet 209
.67.71.165
add_domain_logon_names: At time 05/14/1998 16:30:44 attempting to become
logon server for workgroup SOS on subnet UNI
CAST_SUBNET
05/14/1998 16:30:44 become_domain_master_browser_wins: attempting to
become domain master browser on workgroup SOS, s
ubnet UNICAST_SUBNET.
become_domain_master_browser_wins: querying WINS server at IP
209.67.71.165 for domain master browser name SOS<1b> on
workgroup SOS
become_logon_server_success: Samba is now a logon serverfor workgroup SOS
on subnet UNICAST_SUBNET
05/14/1998 16:30:44 ***** Samba server SOS is now a domain master browser
for workgroup SOS on subnet UNICAST_SUBNET
*****
become_domain_master_browser_bcast: At time 05/14/1998 16:30:44 attempting
to become domain master browser on workgro
up SOS on subnet 209.67.71.165
become_domain_master_browser_bcast: querying subnet 209.67.71.165 for
domain master browser on workgroup SOS
become_logon_server_success: Samba is now a logon serverfor workgroup SOS
on subnet 209.67.71.165
05/14/1998 16:30:54 ***** Samba server SOS is now a domain master browser
for workgroup SOS on subnet 209.67.71.165 *
****
05/14/1998 16:30:58 ***** Samba name server SOS is now a local master
browser for workgroup SOS on subnet 209.67.71
.165 *****
---------------------------------------------------------------------------
I suspect that fail_register line has something to do with it, but
couldn't find that error code in the docs/man pages or usenet.
Any ideas what to do next?
(looks like I'm going to owe several people games :)
Thanks!
--
Philip Hallstrom Technical Director
philip.hallstrom@sierra.com Cendant Software Online Services
http://www.sierra.com/ Cendant Software
On Tue, 12 May 1998, Philip Hallstrom wrote:
> Hi -
> I'll be the first to say I don't completely understand Windows
> networking, but I did get the following to work when everybody
> (clients-w95/server-solaris) were on the same subnet.
>
> W95 boots up and prompts for username,password, and domain. I log in, and
> presto I'm connected and netlogon scripts run and everything is great.
> This is when I'm testing it on a completely isolated subnet.
>
> Now, the server is on it's own subnet, with *all* the W95 clients on
> another subnet and it doesn't work. In fact I can't even see the
shares
> on the server.
>
> Can someone tell me if it's possible to get back where I was? And if
not,
> can you tell me what I need to do to get the shares visible?
>
> It would be worth a game or two (Sierra/Blizzard/Berkely) the the person
> who solves my problem... in addition to my co-workers appreciation in not
> having to hear my rant about it anymore :)
>
> Thanks! -philip
>
> --
> Philip Hallstrom philip@sierra.com
> http://www.sierra.com/ Sierra Online, Inc.
>
>