What i dont understand is the whole external/interface and plugging it in one as opposed to the other. Could you explain in further detail?
I am scouring the net as I write this looking for answers this forum came about as one of my Google searches
Its very straight forward - any equipment you want LMCE to work with/know about goes on the internal network, that is the entire point and single purpose for it. Anything you are absolutely certain you will never need LMCE to touch may go on the external network if you wish. However, why bother? Why not just put everything
on the internal network? This is where LMCE looks for stuff. Then you can plug your external NIC straight into your broadband modem/router, and your "external" network is very trivial indeed!
BUT most critically, the comments above about DHCP were talking about whether your PC and SUSE box are set to request DHCP leases (as opposed to statically assigned), not about whether the core is getting a DHCP address from your external network. Your PCs must be set to DHCP not static.
No your workgroup is irrelevant to discovery - the workgroup is just a NetBIOS name service thing. Discovery is performed at a much lower level during the broadcasting and receiving of DHCP leases which NetBIOS has nothing to do with. Potentially, once discovered and in certain Windows OS's, the workgroup issue may effect whether LMCE can authenticate into your PC for access to data on the shares, but I just put the username and password directly into the share configuration in the LMCE web admin to avoid any of that..