Author Topic: Windows machine on external network  (Read 1049 times)

Gaute

  • Regular Poster
  • **
  • Posts: 33
    • View Profile
Windows machine on external network
« on: March 22, 2009, 01:55:32 am »
Hey!

I know this has been asked before but i have searched for the answer in hours, but can't really find it, so:

I have a LMCE network, with some MD's and a core. The core holds many of my media files. The core is connected to a router which serves the rest the network with only Windows machines. I want to share the files on the LMCE core to the rest of the external network, and it works when i disable the firewall, so:
What port(s) do i have to open to get access from the windows machine with samba?

Gaute

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: Windows machine on external network
« Reply #1 on: March 22, 2009, 02:43:19 am »
Seriously, the correct solution is simply to move the machines on the "external" network to the LMCE network, and thus connect the core directly to your broadband router, ie have no real external network at all. Then all your devices will be able to interact without having to put holes in your firewall.

Gaute

  • Regular Poster
  • **
  • Posts: 33
    • View Profile
Re: Windows machine on external network
« Reply #2 on: March 22, 2009, 07:17:58 pm »
But i have to use the external network (use vpn and stuff), so thats not possible. I just need a answear to my question, not all other ways to solve it.

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5501
  • DOES work for LinuxMCE.
    • View Profile
Re: Windows machine on external network
« Reply #3 on: March 22, 2009, 08:47:33 pm »
We've told you what you need to do, and you still are not listening.

Move your VPN etc to the core, configure it as so.

Otherwise, send us a patch so this configuration will work.

No point in carrying on this thread.

-Thom

Gaute

  • Regular Poster
  • **
  • Posts: 33
    • View Profile
Re: Windows machine on external network
« Reply #4 on: March 22, 2009, 10:16:21 pm »
It is not possible to use the core as the main dhcp because we have our IP phone and modem integrated with the router (which also host our vpn). I have tried to contact our internet/phone provider to set the modem in bridge mode, but it is not possible and for the phone system to work it has to be directly conected to the internet.

My question is simple, and i think the answer is simple to: Which port do i need to open to open for samba access from the external network?

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5501
  • DOES work for LinuxMCE.
    • View Profile
Re: Windows machine on external network
« Reply #5 on: March 22, 2009, 10:24:36 pm »
139.

*shake-head*

-Thom

Gaute

  • Regular Poster
  • **
  • Posts: 33
    • View Profile
Re: Windows machine on external network
« Reply #6 on: March 22, 2009, 10:27:55 pm »
thanks :)

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: Windows machine on external network
« Reply #7 on: March 22, 2009, 10:50:58 pm »
It is not possible to use the core as the main dhcp because we have our IP phone and modem integrated with the router (which also host our vpn). I have tried to contact our internet/phone provider to set the modem in bridge mode, but it is not possible and for the phone system to work it has to be directly conected to the internet.

My question is simple, and i think the answer is simple to: Which port do i need to open to open for samba access from the external network?

Your comment on dhcp indicates that you do not understand how dhcp is supposed to work (generally or in LMCE). There are 2 network segments, LMCE must provide DHCP for the internal segment... please read and understand this http://wiki.linuxmce.org/index.php/Network_Setup  .... nothing in your setup is either unusual nor prevents LMCE from being the DHCP server.

Also, you do not need your broadband device to be a bridge to setup VoIP, it is very common to do so in router mode, and can be done using either the DMZ function of your router or using specific port forwarding and a few config options. It is certainly easier to setup using a bridge, but not required, and leaving your VoIP the way it is means that it will not integrate with LMCE so you loose all that functionality.

Yes, 139 or 445 (which is the more modern equivalent, but either will do) - however, again, doing it this way you will have name resolution issues and have to map drives permanently using IP addresses, leaving you open to failures due to the possiblity of IP changes.

Summary - the approach you are taking means:

1) You will loose the most important Plug n Play system LMCE and in most cases need to add devices manually with the consequent chance of misconfiguration
2) You will loose the ability to have Media Directors as they will be unable to boot, thus limited to a single, hybrid system
3) You will loose VoIP integration with LMCE, thus not be able to distribute telephony around the house, integrated voice mail, IVR, call routing, intelligent handling of calls through house and user modes, onscreen integration, integration with the security system, etc.
4) You will manually have to poke unnecessary holes in the firewall
5) Potentially suffer chronic disconnections between internal and external devices
6) Have to manage 2 groups of devices (internal/external), and coordinate them accessing each other with no name resolution, rather than all being able to access each other without intervention and with name resolution.

Probably other stuff I forgot. But all of this could be avoided completely, as long as you realise that your 2 fears above are completely unfounded and easy to allow within the standard LMCE configuration.


lmce3000

  • Veteran
  • ***
  • Posts: 56
    • View Profile
Re: Windows machine on external network
« Reply #8 on: March 24, 2009, 05:54:37 pm »
I agree with colinjones 100%. You'll do yourself a huge favor by using the system as it is intended to.
Move everything onto your internal network and whatch the magic happen. My system has been running flawlessly
for the past month with no hickups. Printer on the LAN, stand alone Ubuntu machines for work purposes, virtual machines
on another server. Makes accessing and managing your network a lot easier.

John.
* Give a man a fish, you feed him for a day
*Teach a man how to fish, you feed him for a lifetime.