[Samba] cross-subnet domain join issue

[D. Rick Anderson]

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
>
>  
>