virtualbox.org

Perryg wrote:Note: I don't need to see a new screenshot showing the same failure.

OK, no problem. I said what i need to say. There's no need to say no more. If it's a bug, it is. If not, problem is mine. Thanks.

Code: Select all

VBoxManage list natnetworks
NetworkName:    NatNetwork
IP:             10.0.2.1
Network:        10.0.2.0/24
IPv6 Enabled:   No
IPv6 Prefix:    
DHCP Enabled:   Yes
Enabled:        Yes
Port-forwarding (ipv4)
        Rule 1:tcp:[]:111:[10.0.2.10]:111
        Rule 2:udp:[]:111:[10.0.2.10]:111
loopback mappings (ipv4)
        127.0.0.1=2

NetworkName:    NatNetwork2
IP:             10.0.5.1
Network:        10.0.5.0/24
IPv6 Enabled:   No
IPv6 Prefix:    
DHCP Enabled:   Yes
Enabled:        Yes
Port-forwarding (ipv4)
        Rule 1:tcp:[]:111:[10.0.5.10]:111
        Rule 2:udp:[]:111:[10.0.5.10]:111
loopback mappings (ipv4)
        127.0.0.1=2

I know better then some how confusing the GUI is when it comes to port forwarding. They are calling NATnetworks the same as even if you list natnets but they are not the same IMHO. If you look you can see where both NAT ( called Natnetwork ) and NATnetwork2 actually work. I have at time expressed this but so far it has fell on deaf ears or is just not a big enough priority to change anything. Maybe they think this should work but I can tell you it does have issues.

verbal_666,

I am not saying that it is your problem and you need to deal with it, I just don't need to see more screenshots of the same error. I just need to find out why it does not work for you. Did you look and see if you have NAT listed in the pull down and what happens if you select it? Does it accept the forwards?

Perry, are you on an official 5.0.2 build?

Pretty much. There have been no changes to the source in that part of the code in a while so in that sense yes.

But I am still trying to figure out why the OP and now you are seeing this issue while I don't.

I really need to know if selecting NAT instead of NatNetwork allows this to actually work.

I was testing with the configuration of a global NatNetwork.
Now I tried the same in the network setting of a VM with NAT and I get the same error.

At this point it would be good to post a ticket at bugtracker and see what is going on.

I backed up to a version about 4 week ago and it still works for me but I don't test port forwarding enough to know when it became an issue.

On my home Fedora 22 system I still had 4.3.30, where this kind of config works.
After upgrading to 5.0.0/5.0.2 it didn't work in both versions.
Now to find the time to create a bugtracker account...

Thanks martin. I would but it would be useless since I can't reproduce this and they will need data to sort it out.

The problem seems to be fixed (on RHEL 6) in test build 5.0.3 revision 102322 from https://www.virtualbox.org/wiki/Testbuilds

Martin wrote:The problem seems to be fixed (on RHEL 6) in test build 5.0.3 revision 102322 from https://www.virtualbox.org/wiki/Testbuilds

I confirm this new version fixed the problem also on Windows host...

With some work, i made nfs working other Nat Vbox network...

Code: Select all

Port-forwarding (ipv4)
        nfs lockd tcp:tcp:[]:4001:[10.0.2.4]:4001
        nfs lockd udp:udp:[]:4001:[10.0.2.4]:4001
        nfs mountd tcp:tcp:[]:4002:[10.0.2.4]:4002
        nfs mountd udp:udp:[]:4002:[10.0.2.4]:4002
        nfs portmap tcp:tcp:[]:111:[10.0.2.4]:111
        nfs portmap udp:udp:[]:111:[10.0.2.4]:111
        nfs tcp:tcp:[]:2049:[10.0.2.4]:2049
        nfs udp:udp:[]:2049:[10.0.2.4]:2049

[root@linux-VM ~]# rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp   4002  mountd
    100005    1   tcp   4002  mountd
    100005    2   udp   4002  mountd
    100005    2   tcp   4002  mountd
    100005    3   udp   4002  mountd
    100005    3   tcp   4002  mountd
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049
    100227    3   tcp   2049
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049
    100227    3   udp   2049
    100021    1   udp   4001  nlockmgr
    100021    3   udp   4001  nlockmgr
    100021    4   udp   4001  nlockmgr
    100021    1   tcp   4001  nlockmgr
    100021    3   tcp   4001  nlockmgr
    100021    4   tcp   4001  nlockmgr

From the Windows 7 client,

Code: Select all

#mount 10.232.20.175:/home h:
h: ha eseguito la connessione a 10.232.20.175:/home

Esecuzione comando riuscita.

#dir h:
 Il volume nell'unità H non ha etichetta.
 Numero di serie del volume: FBD0-D537

 Directory di H:\

26/08/2015  14:43    <DIR>          marco
17/08/2015  15:58    <DIR>          ..
17/08/2015  15:58    <DIR>          .
               0 File         12.288 byte
               3 Directory   4.264.263.680 byte disponibili

Thanks all for the support

virtualbox.org

Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict

Re: Port Forwarding tcp/udp conflict