All Forums
> Bandwidth Manager
> Current topic
Port mapping and bridging
Started by Vela Gumede
Vela Gumede
Port mapping and bridging 18 October 2016, 04:08 |
|
Re: Port mapping and bridging 18 October 2016, 10:30 |
Admin Registered: 19 years ago Posts: 3 611 |
Vela Gumede
Re: Port mapping and bridging 18 October 2016, 22:02 |
OK Andrew, its the first time I have a client needs to do remote desktop to his server. He wants to connect from outside to his server, he is getting the internet from me wireless. I did DDNS and port forwarding on client side but the traffic is getting blocked to my server. He got internet access but we failing to dial in remotely. Please take me step-by step on how to do port mapping because I think there are some settings I need to do on my server where I installed BWM. If its possible can you login via teamviewer to my server .
|
Re: Port mapping and bridging 18 October 2016, 22:32 |
Admin Registered: 19 years ago Posts: 3 611 |
Let's start with diagram and assume your network looks like this:
<Client server> - <BWM Server> - <Router> - <Internet>
This also assumes your client's server doesn't have a public IP address. In that case, the client would connect to port X and your router's IP address. You will need to configure the router to pass traffic from port X to the server's IP address.
Then if the server was connected directly to the router, that'd be all. However we also have to pass through BWM server - if you are using bridging, that would be automatic. If you are using RRAS or ICS, you may have to configure the router's port forwarding to send data to the BWM server instead and from there you can forward it to client's server.
The easiest solution though is to tell the client to use Teamviewer instead - it works behind NAT and doesn't require port forwarding.
<Client server> - <BWM Server> - <Router> - <Internet>
This also assumes your client's server doesn't have a public IP address. In that case, the client would connect to port X and your router's IP address. You will need to configure the router to pass traffic from port X to the server's IP address.
Then if the server was connected directly to the router, that'd be all. However we also have to pass through BWM server - if you are using bridging, that would be automatic. If you are using RRAS or ICS, you may have to configure the router's port forwarding to send data to the BWM server instead and from there you can forward it to client's server.
The easiest solution though is to tell the client to use Teamviewer instead - it works behind NAT and doesn't require port forwarding.
Vela Gumede
Re: Port mapping and bridging 18 October 2016, 23:50 |
|
Re: Port mapping and bridging 19 October 2016, 00:23 |
Admin Registered: 19 years ago Posts: 3 611 |
Vela Gumede
Re: Port mapping and bridging 19 October 2016, 01:36 |
The BWM server is connected to mikrotik router and the second card connected to Ethernet switch then to clients
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\user>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : EWN
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet
NIC
Physical Address. . . . . . . . . : CC-5D-4E-6A-F0-50
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc2d:a2f9:992a:ac6c%14(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 399269198
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-49-88-A4-70-71-BC-77-94-CA
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82578DM Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 70-71-BC-77-94-CA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6837:b012:acd1:2623%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.248.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.248.1
DHCPv6 IAID . . . . . . . . . . . : 242250172
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-49-88-A4-70-71-BC-77-94-CA
DNS Servers . . . . . . . . . . . : 192.168.248.1
8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{23439379-EAF2-411D-A209-4D52B2F9697F}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\user>
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\user>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : EWN
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet
NIC
Physical Address. . . . . . . . . : CC-5D-4E-6A-F0-50
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc2d:a2f9:992a:ac6c%14(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 399269198
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-49-88-A4-70-71-BC-77-94-CA
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82578DM Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 70-71-BC-77-94-CA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6837:b012:acd1:2623%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.248.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.248.1
DHCPv6 IAID . . . . . . . . . . . : 242250172
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-49-88-A4-70-71-BC-77-94-CA
DNS Servers . . . . . . . . . . . : 192.168.248.1
8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{23439379-EAF2-411D-A209-4D52B2F9697F}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\user>
|
Re: Port mapping and bridging 19 October 2016, 10:19 |
Admin Registered: 19 years ago Posts: 3 611 |
Vela Gumede
Re: Port mapping and bridging 19 October 2016, 17:51 |
|
Re: Port mapping and bridging 19 October 2016, 18:02 |
Admin Registered: 19 years ago Posts: 3 611 |
In this case, as you are not telling how and if you configured Microtik appropriately, here is how to configure port forwarding with ICS. It is not related to our product by the way - you will need to make your own research on how to configure it.