Messages

1

Mitel MiVoice Business/MCD/3300 / MCD 3300 with MSL/MBG Registering Teleworker sets

« on: August 18, 2022, 11:20:47 AM »

First time posting,,,

Relocated customers office to new location with new internet provider. All worked fine till reprogrammed for new IP in MBG.
I have a MCD3300 with MSL w/ MBG blade deployed as DMZ Network. The only difference between old site and new is they had 1 public IP address (24.192.123.19) and the New location has 5 public IP address. (199.36.196.71-199.36.196.75). I changed the MBG settings for DMZ Network Config to 199.36.176.72->10.10.101.2. and the MCD stayed the same 172.20.101.10. All local sets are up and the MSL-Nupoint vSets registered and are working as expected.  When going to the remote sites and changing the new static IP address of 199.36.176.72 they fail TFTP. 

They have their own Network personnel and he is stating that he opened all ports till we could get this working but it took 3 days just to get the internal network to work to the MSL so

Thoughts? and any good test I can do to show where the problem is.


I did some remote port testing into their public IP.

PS C:\Windows\system32> Test-NetConnection -computername 199.36.196.72 -Port 69
WARNING: TCP connect to (199.36.196.72 : 69) failed


ComputerName           : 199.36.196.72
RemoteAddress          : 199.36.196.72
RemotePort             : 69
InterfaceAlias         : Wi-Fi
SourceAddress          : 192.168.1.155
PingSucceeded          : True
PingReplyDetails (RTT) : 14 ms
TcpTestSucceeded       : False




PS C:\Windows\system32> Test-NetConnection -computername 199.36.196.72 -Port 80


ComputerName     : 199.36.196.72
RemoteAddress    : 199.36.196.72
RemotePort       : 80
InterfaceAlias   : Wi-Fi
SourceAddress    : 192.168.1.155
TcpTestSucceeded : True




PS C:\Windows\system32> Test-NetConnection -computername 199.36.196.72 -Port 20001
WARNING: TCP connect to (199.36.196.72 : 20001) failed


ComputerName           : 199.36.196.72
RemoteAddress          : 199.36.196.72
RemotePort             : 20001
InterfaceAlias         : Wi-Fi
SourceAddress          : 192.168.1.155
PingSucceeded          : True
PingReplyDetails (RTT) : 14 ms
TcpTestSucceeded       : False




PS C:\Windows\system32> Test-NetConnection -computername 199.36.196.72 -Port 6800
WARNING: TCP connect to (199.36.196.72 : 6800) failed


ComputerName           : 199.36.196.72
RemoteAddress          : 199.36.196.72
RemotePort             : 6800
InterfaceAlias         : Wi-Fi
SourceAddress          : 192.168.1.155
PingSucceeded          : True
PingReplyDetails (RTT) : 11 ms
TcpTestSucceeded       : False




PS C:\Windows\system32> Test-NetConnection -computername 199.36.196.72 -Port 6802
WARNING: TCP connect to (199.36.196.72 : 6802) failed


ComputerName           : 199.36.196.72
RemoteAddress          : 199.36.196.72
RemotePort             : 6802
InterfaceAlias         : Wi-Fi
SourceAddress          : 192.168.1.155
PingSucceeded          : True
PingReplyDetails (RTT) : 21 ms
TcpTestSucceeded       : False




PS C:\Windows\system32> Test-NetConnection -computername 199.36.196.72 -Port 3999
WARNING: TCP connect to (199.36.196.72 : 3999) failed


ComputerName           : 199.36.196.72
RemoteAddress          : 199.36.196.72
RemotePort             : 3999
InterfaceAlias         : Wi-Fi
SourceAddress          : 192.168.1.155
PingSucceeded          : True
PingReplyDetails (RTT) : 14 ms
TcpTestSucceeded       : False




PS C:\Windows\system32> Test-NetConnection -computername 199.36.196.72 -Port 443


ComputerName     : 199.36.196.72
RemoteAddress    : 199.36.196.72
RemotePort       : 443
InterfaceAlias   : Wi-Fi
SourceAddress    : 192.168.1.155
TcpTestSucceeded : True




PS C:\Windows\system32> 
[/size][/color]