so i guess this is kind of a strange, and seemingly complicated problem. I have a DMVPN (for arguments sake, lets just say its a site-to-site, as the functionality seems the same so far) set up between 2 cisco routers between our corp HQ and a branch office. as far as the vpn tunnel goes, everything seems to be working fantastic. traffic flows fine in both directions, i can ssh, vnc, and seemingly use (almost) any protocol i need to from one side to the other.
oh the HQ end of the vpn tunnel, we have a samba domain controller set up on a debian etch machine, with samba handing out various network shares to the users. on the branch office end, we will have nothing but windows users that need to log into this domain and map those shares to be able to function from one day to the next. now the problem that we're having thus far is that the windows clients on the branch end cannot even SEE the domain on the HQ end of the vpn tunnel, regardless of what ive tried thus far.
So far, ive tried to use a lmhosts file on the client machines to point them to the domain controller, to no avail, setting the IP of the domain controller in the client machine's dns did nothing, and i even found this link:
http://support.microsoft.com/kb/244474 that made me wonder if the issue could be caused by UDP packet fragmentation due to the vpn tunnel, but that registry hack didnt work either.
at this point, im kind of at the end of my rope wondering why in the world my clients cant see the domain at all from the other end of a vpn tunnel, when those same machines work just fine when theyre on the local LAN. im open to suggestions folks, any help would be GREATLY appreciated.
