irBosOtter
Expert Member
ive been told that vuma blocks ports. found out when helping my father with his voip phone. the isp had it unblocked.
Probably the ISP lying to cover their own mistake, Vumatel doesn't block any ports
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
ive been told that vuma blocks ports. found out when helping my father with his voip phone. the isp had it unblocked.
Probably the ISP lying to cover their own mistake, Vumatel doesn't block any ports
If you do a "route print" in command prompt while connected to the VPN (asuming you are using a windows pc) does it show that route?
helped a friends mother sign up recently, on the website they ask if youre going to use voip with anyone, because it needs to be enabled(unblocked) with vuma, there is a checkbox
No need, it works on a different connection.What account are you using to log into server, on that account, try adding your computer name to the "Logon To" list in AD.
That's on the ISP side not Vuma at all, what ISP was that? SIP works fine on Vumatel, nothing needs to be unblocked
They can't block ports within a VPN tunnel.No need, it works on a different connection.
They can't block ports within a VPN tunnel.
What other connection are you using? I reckon the RDP connection you are trying is not going through the VPN, but on your normal internet connection
No need, it works on a different connection.
Sounds like a bit of trial and error, do you have the option to use: RD Gateway ?
Have you tried with both hostname and IP ?
What is your IP once on the VPN ?
Turns out the VPN IP Range was the same as my home network IP Range, and the machine I was RDP'ing/Pinging had the same IP address as my machine.
What a stupid yet confusing error..
Thankfully all sorted now hahaha!
The ip ranges on your home lan are the same as your office ones?
Lol. Called itTurns out the VPN IP Range was the same as my home network IP Range, and the machine I was RDP'ing/Pinging had the same IP address as my machine.
What a stupid yet confusing error..
Thankfully all sorted now hahaha!