Mweb VPS incomming ports blocked

[HaltAndCatchFire]

Hi,
Maybe i'm just missing something obvious here, but does mweb block certain ports going into their vps network?

We have a cloud hosting package with them and as of early this morning I have been trying to get ssh or ftp or any non http services going. The server runs windows server 2008 r2, but it only responds to requests on port 80.

I believe the issue is not on our server's side, as I can access services locally and have added firewall rules locally.

Also the packets seems to stop at 164.75.28.196.netactive.net as shown by the tcptraceroute's below:


tcptraceroute 41.xx.xx.xx 22
Selected device eth0, address 192.168.0.19, port 48498 for outgoing packets
Tracing the path to 41.xx.xx.xx on TCP port 22 (ssh), 30 hops max
1 192.168.0.1 0.638 ms 0.623 ms 0.659 ms
2 #DSL-IP# 12.016 ms 9.711 ms 10.000 ms
3 197-80-96-138.jhb.mweb.co.za (197.80.96.138) 12.027 ms 12.378 ms 12.048 ms
4 vl-92.vic-hscore-2.mweb.co.za (197.80.2.2) 12.501 ms 12.216 ms 12.399 ms
5 197-80-96-58.jhb.mweb.co.za (197.80.96.58) 12.116 ms 11.793 ms 12.486 ms
6 197-81-229-4.jhb.mweb.co.za (197.81.229.4) 13.252 ms 12.493 ms 24.740 ms
7 197-81-229-15.jhb.mweb.co.za (197.81.229.15) 20.802 ms 12.729 ms 12.641 ms
8 164.75.28.196.netactive.net (196.28.75.164) 19.113 ms 12.719 ms 12.808 ms
9 *^C

tcptraceroute 41.xx.xx.xx 21
Selected device eth0, address 192.168.0.19, port 57106 for outgoing packets
Tracing the path to 41.xx.xx.xx on TCP port 21 (ftp), 30 hops max
1 192.168.0.1 1.191 ms 0.546 ms 0.652 ms
2 #DSL-IP# 11.911 ms 10.536 ms 10.691 ms
3 197-80-96-138.jhb.mweb.co.za (197.80.96.138) 12.688 ms 12.309 ms 12.289 ms
4 vl-92.vic-hscore-2.mweb.co.za (197.80.2.2) 12.354 ms 12.799 ms 12.616 ms
5 197-80-96-58.jhb.mweb.co.za (197.80.96.58) 12.526 ms 12.163 ms 12.334 ms
6 197-81-229-4.jhb.mweb.co.za (197.81.229.4) 13.314 ms 13.735 ms 12.992 ms
7 197-81-229-15.jhb.mweb.co.za (197.81.229.15) 13.781 ms 13.221 ms 12.913 ms
8 164.75.28.196.netactive.net (196.28.75.164) 14.766 ms 13.668 ms 12.405 ms
9 * *^C

tcptraceroute 41.xx.xx.xx 80
Selected device eth0, address 192.168.0.19, port 40581 for outgoing packets
Tracing the path to 41.xx.xx.xx on TCP port 80 (http), 30 hops max
1 192.168.0.1 0.702 ms 0.644 ms 0.641 ms
2 #DSL-IP# 11.645 ms 9.949 ms 10.230 ms
3 197-80-96-138.jhb.mweb.co.za (197.80.96.138) 13.065 ms 12.160 ms 12.295 ms
4 vl-92.vic-hscore-2.mweb.co.za (197.80.2.2) 12.197 ms 12.296 ms 12.457 ms
5 196.22.169.9 12.160 ms 12.384 ms 12.110 ms
6 197-80-96-58.jhb.mweb.co.za (197.80.96.58) 13.075 ms 12.303 ms 12.172 ms
7 197-81-229-4.jhb.mweb.co.za (197.81.229.4) 13.192 ms 13.069 ms 13.062 ms
8 197-81-229-15.jhb.mweb.co.za (197.81.229.15) 14.195 ms 13.555 ms 12.846 ms
9 164.75.28.196.netactive.net (196.28.75.164) 14.459 ms 12.976 ms 13.179 ms
10 #Server-IP# [open] 12.878 ms 13.778 ms 18.628 ms

 

[Tinuva]

Could be a firewall still on the VPS, even if you can access those ports locally on that machine. Firewalls are much more relaxed to local requests vs external requests.

 

[w1z4rd]

SSH into a windows machine? Have you installed a SSHD?

Have you tried to remote desktop in?

 

[RNJudas]

SSH into a windows machine? Have you installed a SSHD?

Have you tried to remote desktop in?

 

[w1z4rd]

Since he has not replied, I am assuming something like this is the case

 

[RNJudas]

Since he has not replied, I am assuming something like this is the case

Ahhh Ghoti.... I just lolled.... I am still Lolling... Goooootttt times...