Map a drive behind a NAT Firewall

[GeSuN]

Hi,

In short, what are the ports needed to be able to map a drive from another computer? I know how to do port forwarding and everything, I just need to know the ports used in MS Networks for sharing...

Thanks!

GeSuN

 

[JackMDS]

Hardware (Router) Firewall NAT does not relate to local mapping.

If you have Software Firewall then open all ports in the Trusted Zone.

That means no port blocking between computers that are inside your LAN.

The make sure that your Sharing is configured correctly then Map the ports.

Enter the term mapping into Windows own Help it will tell you what to do.

 

[GeSuN]

I think you did not understand my question...


I've got the following architecture :

DSL -> Router1 -> 192.168.0.X (server) + 192.168.0.Y (Router2) -> Router2 -> 192.168.1.W

I'm not trying to share it behind the same router! I want to share a drive from the 192.168.1.W computer to the 192.168.0.X server computer.

But my problem is that the Router2 is in Gateway mode, so it has NAT enabled and I don't want to set it as a router wich would allow me to map the drive without any problem, but would have the drawback of opening my 192.168.1.0 network to the 192.168.0.0.

So I want to open ports in the Router2 to be able to share the drive through it. Yes I'm gonna loose some security, but I'm just wondering if that's something feasable.

 

[Nothinman]

What kind of router has a router mode with no ACLs?

Anyway the ports depend on the OS, generally 137,139 and 445 should cover them all. Why not just use a packet sniffer to see what kind of traffic goes when you issue the 'net use' command?

 

[ToeJam13]

You can't do this.

NetBIOS over TCP/IP does something called "IP embedding". This is where a program inserts an IP address at the application data level.

When a NetBIOS packet goes through a NAT address on a firewall, it translates the destination address at the IP transport layer. The firewall knows nothing about how NetBIOS works, so the IP in the application data layer is untouched.

When the server receives the packet, it breaks the packet down and NetBIOS looks inside the application data. There, it sees a foreign IP address and gets confused.

If you still want to try things, ports 137/UDP and 139/TCP are the ones you want. Keep in mind that your network neighborhood won't work if you're part of a workgroup - NetBIOS uses UDP network broadcasts to announce members within the same workgroup. Since you're using two different subnets, you'll have to manually set a share via the target server's IP address. Something like this should work:

net use * \\192.168.0.X\Sharename

 

[GeSuN]

What kind of router has a router mode with no ACLs?

Linksys routers


Thank you very much ToeJam13 for your answer... knowing why you can't do it is much better than just knowing that you can't do it.

 

[GeSuN]

Just to let you know guys, I tried it this morning and it works like a charm

I have now a 192.168.1.W drive on my 192.168.0.X server