How can I troubleshoot file sharing between a client on one domain and a home network (different domain)?

Question by Tom D: How can I troubleshoot file sharing between a client on one domain and a home network (different domain)?
I’ve got a server (192.168.0.1) setup as both a DC, DHCP, DNS, WINS and File Server (phew) at home with the domain name “olympus.local” and I’m trying to access network shares on it using my work computer which is on domain “company.com”. I’ve setup DHCP to push a router IP (diff server), DNS Server (192.168.0.1), DNS Domain Name (olympus.local) and WINS/NBNS Servers (192.168.0.1)… all of which seem to take hold on the foreign client except the domain name for some reason (DNS suffixes don’t mention olympus at all… just my work DNS suffixes).

Any ideas on how I can get this stupid laptop to access the shares on my servers? I can ping the server and DNS resolves it if I use the FQDN (until I installed WINS I could just ping the hostname even… WINS seems to have broken that… odd, but acceptable [maybe]).

Well, I guess I should have stipulated that I don’t have the money/extra boxes lying around to install linux or purchase fancy equipment ;)

Best answer:

Answer by FörtyTwö
Install a GOOD Linux distro, (free as in free to use,change,modify and share what you learn)
Then the WINS is foobar.
DHCP on the TCP/IP network and decide which is Client and which is Host.
If you are moving state secrets or private company data around, the Internet is NOT the place to do that.
Get an External HDD and cpy/move the data.
It also makes a good Backup utility, and not much can beat that.

Know better? Leave your own answer in the comments!

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>