Setup Windows sharing for Port forwarding conflict with TC file sharing; disabled file sharing my iMAC Time Machine cannot find the (must remove) TC

Question

Setup Windows sharing for Port forwarding conflict with TC file sharing; disabled file sharing my iMAC Time Machine cannot find the (must remove) TC

Is it a bug ? limitation ? design deficiency ...

my iMAC wired to TC

windows sharing port fowarding setup to iMAC disks, TC disk file sharing is off to avoid conflict

outside TC (over internet, in fact, another private LAN, on double NAT), a windows PC can use on 445 to map iMAC folders

but then the Time Machine lost the TC (without the TC disks file sharing)

iMac

Posted on Apr 12, 2013 7:46 PM

Reply

Answer 1

Apr 12, 2013 8:26 PM in response to Raymond Leung

It is very odd, because iMac will use port 548 to connect to AFP.. It should not be using 445.

In the mac try and mount the TC disk manually.. you will need to turn on the file sharing again.. but by itself that should not be a problem.. in finder.. use main menu.. go, connect to server.

Type in AFP://TCname or TCIPaddress where you replace it with the actual IP or Name of course.

The issue may be caused by the iMac incorrectly using SMB to connect.

TC offers both AFP and SMB connection.

http://support.apple.com/kb/ts1629

If you are opening SMB to internet you will get hacked before long.. so forwarding port 445 is extremely risky.

Reply

Answer 2

Apr 12, 2013 9:52 PM in response to LaPastenague

Not ... quite exactly my problem.

I turn on File Sharing at TC, my iMAC (direct ethernet connect TC) can see the TC immediately. So the Time Machine can run.

But at TC, i want to add Port (mapping Forwarding with Windows Sharing (purpose is to make my iMAC folder sharing to outside Windows PC), TC flagged me conflict 137-138 UDP already turned on at File Sharing ...

I stopped File Sharing at TC, my Time Machine cannot find the TC (nor using Finder Go Connect IP), but then I add Port Forwarding (137-139,445), then my Windows PC outside (WAN) can see my iMAC folder.

I think Apple TC has bug or design limitation to allow both usage the same time.

Reply

Answer 3

Apr 12, 2013 9:54 PM in response to Raymond Leung

Reply

Answer 4

Apr 12, 2013 11:29 PM in response to Raymond Leung

I would say apple doesn't really care.. since they do not expose SMB to the internet.. as most ISP simply block SMB as the risk is far too great. You will get hacked.. it is not if.. merely when.

Why do you need UDP ports. For simple SMB access you don't need it.

The conflict is with UDP which is due to netbios setup. WINS is not used anymore.. I would simply remove the UDP. You will have to use Mac IP rather than name but that should not make any difference.

137	UDP	Windows Internet Naming Service (WINS)	-	netbios-ns	-
138	UDP	NETBIOS Datagram Service	-	netbios-dgm	Windows Datagram Service, Windows Network Neighborhood

Note there is only one safe way to do this.. if you want to access the computer.. use vpn.

All the Mac's have inbuilt pptp at least. Otherwise you are exposing the most readily hacked port in the world.

Reply

Answer 5

Apr 12, 2013 11:39 PM in response to LaPastenague

well ... thanks discussing.

My TC is on double NAT, not really directly to Internet. My windows PC "outside" is in fact on private LAN outside (172.22.x.x) which then go to LAN web gateway properly under corporate firewall protection. My iMAC's (wired to TC ethernet port) is on TC private LAN (10.0.x.x) with DHCP reserved Fixed IP ...

Yes, windows (new XP, 7...) uses 445 ... i need that, ... but when i set only 445 ... the TC still give me the red arrow saying TCP 445 is in conflict ...

I am giving up.... or thinking of different ways to share my iMAC folder to the "outside" windows PC

Thanks so much info. anyway.

Reply

Answer 6

Apr 13, 2013 12:35 AM in response to Raymond Leung

The usual trick we use is port translate.

So use a different port on the WAN side and translate to the LAN.. but you will need to mess things around to get SMB working on non-standard ports.

VPN is still the way to do it.

Or do you need to use double NAT.. ??

Couldn't the Mac just exist on the LAN side.. with the windows computer.. and put the TC into bridge.

You can also try use SMB to the TC IP internal address.. you might also find that works.. then you would need to copy the files to the TC and they can be picked up from there.. I am sure I have seen people do that.

Reply