Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
1. The office NT network is on a 10.x.x.x network, and the PDC is located 3000km away and is NOT under my control.
2. A network of Unix development machines on a 192.0.0.x network, currently under my control.
3. I have built a stand-alone Linux Samba server and assigned it an IP of 192.0.0.253 (the same sub-net as the Unix boxes).
I do NOT wish to add the Samba server to the NT domain, as "Company Policy" will not permit such things. The NT workstations have additional 192.0.0.x IP's that allow us to connect to the Unix development machines, for ftp, ssh and X connections. I am hoping to access the Samba server from these NT workstations, so that we can manage software control. Now, the Samba server appears on the NT workstation's as a Workgroup, yet connections to the server result in a long timeout followed by "unable to find server" messages. I have encrypted password enabled on the Samba server, but suspect the workstations are trying to find the Samba server via the PDC.
I fully tested the Samba server from other Linux machines running smbclient -L, and mounting the Samba shares etc, prior to locating the machine in the office (I built the Linux machine at home).
Not knowing *much* about M$ machines, can I acheive my goal and how? Thanks.
The NT workstations have "secondary" IP's defined, and yes they can all reach the 192.0.0.x Unix machines and also the Samba server. I can ping, telnet,ssh & ftp to all 192.0.0.x machines.
The Samba server appears in the NT browse lists.
Having read more man and HOWTO's this weekend, I now know that I have to either config the Samba server to use the existing NT PDC to authenticate users, or, add each NT machine as "machine" type users on the Samba machine.
Will have a damn good shot at this again come Monday.
I have spent too much time away from M$ to know what the hell is going on in Bill land.
Right, got it sorted. I added a route on the Samba server (a 192.0.0.0 network) to route to the 10.x.x.x network of the NT workstations. Works a treat, we have all users (developers) happilly mounting Samba shares.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.