Re: [Samba] cross-subnet domain join issue
Okay, I'm clearly not as smart as I'd hoped, as I failed to have my Samba PDC connect to our WINS server. Adding the server IP has changed things, but I'm still experiencing difficulties. Here's my nmdb log from startup there's some strange stuff in here. - [2003/09/08 11:29:20, 0] nmbd/nmbd_nameregister.c:register_name_response(130) register_name_response: server at IP 128.95.113.168 rejected our name registration of LOGOS00 IP 128.95.113.9 with error code 6. [2003/09/08 11:29:20, 0] nmbd/nmbd_mynames.c:my_name_register_failed(36) my_name_register_failed: Failed to register my name LOGOS00 on subnet 128.95.113.9. [2003/09/08 11:29:20, 0] nmbd/nmbd_namelistdb.c:standard_fail_register(283) standard_fail_register: Failed to register/refresh name LOGOS00 on subnet 128.95.113.9 [2003/09/08 11:29:20, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) add_domain_logon_names: Attempting to become logon server for workgroup LOGOS on subnet 128.95.113.9 [2003/09/08 11:29:20, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) add_domain_logon_names: Attempting to become logon server for workgroup LOGOS on subnet UNICAST_SUBNET [2003/09/08 11:29:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(327) become_domain_master_browser_wins: Attempting to become domain master browser on workgroup LOGOS, subnet UNICAST_SUBNET. [2003/09/08 11:29:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(341) become_domain_master_browser_wins: querying WINS server from IP 0.0.0.0 for domain master browser name LOGOS1b on workgroup LOGOS [2003/09/08 11:29:25, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup LOGOS on subnet 128.95.113.9 [2003/09/08 11:29:41, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) become_logon_server_success: Samba is now a logon server for workgroup LOGOS on subnet UNICAST_SUBNET [2003/09/08 11:29:41, 0] nmbd/nmbd_become_dmb.c:become_domain_master_query_fail(252) become_domain_master_query_fail: Error 0 returned when querying WINS server for name LOGOS1b. [2003/09/08 11:29:43, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) * Samba name server LOGOS is now a local master browser for workgroup LOGOS on subnet 128.95.113.9 * [2003/09/08 11:30:03, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(350) find_domain_master_name_query_fail: Unable to find the Domain Master Browser name LOGOS1b for the workgroup LOGOS. Unable to sync browse lists in this workgroup. [2003/09/08 11:34:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(327) become_domain_master_browser_wins: Attempting to become domain master browser on workgroup LOGOS, subnet UNICAST_SUBNET. [2003/09/08 11:34:20, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(341) become_domain_master_browser_wins: querying WINS server from IP 0.0.0.0 for domain master browser name LOGOS1b on workgroup LOGOS [2003/09/08 11:34:40, 0] nmbd/nmbd_become_dmb.c:become_domain_master_query_fail(252) become_domain_master_query_fail: Error 0 returned when querying WINS server for name LOGOS1b. [2003/09/08 11:39:25, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(327) become_domain_master_browser_wins: Attempting to become domain master browser on workgroup LOGOS, subnet UNICAST_SUBNET. [2003/09/08 11:39:25, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(341) become_domain_master_browser_wins: querying WINS server from IP 0.0.0.0 for domain master browser name LOGOS1b on workgroup LOGOS [2003/09/08 11:39:25, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95) process_logon_packet: Logon from 128.95.113.168: code = 0x12 [2003/09/08 11:39:25, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95) process_logon_packet: Logon from 128.95.113.168: code = 0x12 [2003/09/08 11:39:46, 0] nmbd/nmbd_become_dmb.c:become_domain_master_query_fail(252) become_domain_master_query_fail: Error 0 returned when querying WINS server for name LOGOS1b. Some googling tells me that its okay that it might be okay for the IP to be listed as 0.0.0.0... but I'm not so sure. Can anyone confirm? In addition, any theories as to what exactly Error 0 might be... what about Error 6? Thanks, Sean On Sat, 2003-09-06 at 04:34, Richard Coates wrote: Hi Sean, all you need for cross-subnet browsing/domain functionality is correct routing...no port blocking/firewall problems across routers etc. ONE only wins server with ALL severs/clients using it. netbios over tcp (I havent tried setup without this) correctly setup pdc and Xp/Nt/2k/linux as local subnet master browsers. All is explained nicely in the old browsing.txt doc, and probably included in the new samba3 docs. Richard Coates. On Sat, 2003-09-06 at 08:04, Sean Kellogg wrote: So, I already sent this message once before (yesterday), but I can't seem to find
[Samba] cross-subnet domain join issue
So, I already sent this message once before (yesterday), but I can't seem to find it on the archives (and have received no responses), so I'm wondering if it got bounced. If it didn't and I'm just being ignore, then I'll just stay put over here in the corner... if it did, please take a read and see if you can help. -Sean -- I am one hurdle away from finishing my test PDC with ldap and password sync. Its been a hair raising effort... and if I can solve this one issue, we'll be ready to kick our Windows PDC out the window. When I attempt to initially join the domain ( LOGOS ) from a win2K client residing on a different subnet, I get the following: The following error occured validating the name LOGOS The condition may be caused by a DNS lookup problem. For information about troubleshooting common DNS lookup problems, please see the following Microsoft Website: http://go.microsoft.com/fwlink/?LinkID=5171 The specified domain either does not exist or could not be contacted This is the same error I would get on clients residing on the same subnet that didn't have NetBIOS over TCP/IP enabled. Once enabled, I was able to join without incident. However this does not appear to be the issue with clients residing on other subnets, as they are properly configured. Adding to complications, I am certain that the server running the domain (also named LOGOS) can be seen from other subnets by doing lookups on //LOGOS/. Documentation on the subject seems to indicate that this shouldn't be an issue... the tough part is supposed to be browsing, but I can't start tackling that issue until I'm join to the domain in the first place. Thanks for any assistance, Sean -- Sean Kellogg University of Washington Biostatistics Department - Linux Guy e: [EMAIL PROTECTED]p: 5-9176 Linux is to the internet what duct tape is to everything else -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] cross-subnet domain join issue
Have you tried using 'remote announce' ? add: remote announce = 192.168.1.255/DOMAIN_NAME to the global section of your smb.conf file using your remote network and domain of course. If that doesn't work, then try enabling Wins support on your Samba server, and setting it as the primary wins resolution server on your workstations. (you may want to do this anyway) HTH Rick Sean Kellogg wrote: So, I already sent this message once before (yesterday), but I can't seem to find it on the archives (and have received no responses), so I'm wondering if it got bounced. If it didn't and I'm just being ignore, then I'll just stay put over here in the corner... if it did, please take a read and see if you can help. -Sean -- I am one hurdle away from finishing my test PDC with ldap and password sync. Its been a hair raising effort... and if I can solve this one issue, we'll be ready to kick our Windows PDC out the window. When I attempt to initially join the domain ( LOGOS ) from a win2K client residing on a different subnet, I get the following: The following error occured validating the name LOGOS The condition may be caused by a DNS lookup problem. For information about troubleshooting common DNS lookup problems, please see the following Microsoft Website: http://go.microsoft.com/fwlink/?LinkID=5171 The specified domain either does not exist or could not be contacted This is the same error I would get on clients residing on the same subnet that didn't have NetBIOS over TCP/IP enabled. Once enabled, I was able to join without incident. However this does not appear to be the issue with clients residing on other subnets, as they are properly configured. Adding to complications, I am certain that the server running the domain (also named LOGOS) can be seen from other subnets by doing lookups on //LOGOS/. Documentation on the subject seems to indicate that this shouldn't be an issue... the tough part is supposed to be browsing, but I can't start tackling that issue until I'm join to the domain in the first place. Thanks for any assistance, Sean -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] cross-subnet domain join issue
I am one hurdle away from finishing my test PDC with ldap and password sync. Its been a hair raising effort... and if I can solve this one issue, we'll be ready to kick our Windows PDC out the window. When I attempt to initially join the domain ( LOGOS ) from a win2K client residing on a different subnet, I get the following: The following error occured validating the name LOGOS The condition may be caused by a DNS lookup problem. For information about troubleshooting common DNS lookup problems, please see the following Microsoft Website: http://go.microsoft.com/fwlink/?LinkID=5171 The specified domain either does not exist or could not be contacted This is the same error I would get on clients residing on the same subnet that didn't have NetBIOS over TCP/IP enabled. Once enabled, I was able to join without incident. However this does not appear to be the issue with clients residing on other subnets, as they are properly configured. Adding to complications, I am certain that the server running the domain (also named LOGOS) can be seen from other subnets by doing lookups on //LOGOS/. Documentation on the subject seems to indicate that this shouldn't be an issue... the tough part is supposed to be browsing, but I can't start tackling that issue until I'm join to the domain in the first place. Thanks for any assistance, Sean -- Sean Kellogg University of Washington Biostatistics Department - Linux Guy e: [EMAIL PROTECTED]p: 5-9176 Linux is to the internet what duct tape is to everything else signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
