Unable to ping own MWEB IP Address

XperiAnce

XperiAnce

Senior Member
Joined
Feb 23, 2005
Messages
630
Reaction score
205
Hey everyone.

I've been having this problem for several weeks now. I am unable to ping my own MWEB IP Address, and thus cannot use services like Remote Desktop or anything like that as my IP Address doesn't 'work'.

I've made no changes to my router (Netgear DG834GT) and have re-checked all possible settings (Firewall, Router Settings, you name it)

I'm not being a moron, I promise I'm using the correct IP Address and have not made any policy changes to my Router that would prevent this from happening.

Anyone on MWEB, please try ping your own IP Address and let me know if it successfully returns, or if it's just unique to my account.
 
Remember that it's your router, not your pc, that will have the ip address assigned by Mweb. What you would need to do is set up port forwarding on your router to allow it to forward requests to your pc. You would need to set up a rule on your router that allows any traffic routed to port 3389 (I think) to be forwarded to your pc. You would probably need to set a static ip address on your pc - if you have more than one pc at home then you'd probably be using dhcp so wouldn't necessarily get the same ip.
 
Thanks for the reply hammell. I was using Remote Desktop successfully in the past - it literately one day stopped working. Ports were already set up to forward 3389 to the computer in question. That computer has an assigned ip address in the DHCP table so it always gets 192.168.0.28.

The issue is that I try ping the IP Address that the router gives my Internet Session, but it just doesn't ping. Just says request timed out. For obvious reasons, I can't give out the full address on a public forum but it is a 41.135.*.* address. The fact that I can't ping the basic IP address leads me to believe that the error is most likely not on my side.

I can confirm that Protected Access is switched off (and has been switch off since April, when I switched to 384k Uncapped).
 
Last edited:
Routers can also be config'd to respond or not respond to ping replies (which is most likely whats happening if you're not forwarding the ping port)
 
What happens when you traceroute? where does it die?
The router has a firewall log, do you see the traffic hitting your router at all?
 
I wouldn't rely too much on pings/icmp. Most routers these days are not configured to reply to pings. If you have opened a port and are sure forwarding is correctly set up you can test this by telnet. From a command prompt:

telnet X.X.X.X 3389

If the prompt goes blank, that means that the port is opened (substitute 3389 for anything). If the prompt just sits there, it's not open.
 
The things is, I did not make a single alteration to my Router, I woke up one morning, tried to remote desktop into my computer and it didn't work.
Under the Netgears Security Settings, "Respond to Ping" is checked - even if it wasn't checked, I wouldn't be able to ping it (port 80) but would still be able to remote desktop into it (port 3389) - however I can't remote desktop into it as when I tell the Remote Desktop application to connect to my IP, my IP doesn't 'exist' (Request Timed Out). Remote Desktop is working fine, as I can remote desktop locally by using 192.168.0.28.

There's no way to say this without sounding pompous, arrogant or sarcastic so please don't read it as such, but I know what I'm doing - I appreciate all the input but I swear that all Port Forwarding is set up correctly and zero Security Policy Changes were made that could have caused this.

Here's the results of the Tracert. I've blocked out some private information with !!!!'s, so ignore those :)

C:\>tracert 41.135.!!.!!

Tracing route to 41-135-!!-!!.dsl.mweb.co.za [41.135.!!.!!]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms server.internal.!!.co.za [192.168.1.200]
2 <1 ms <1 ms <1 ms 10.0.0.254
3 16 ms 15 ms 16 ms 41.0.!!.!!
4 18 ms 18 ms 17 ms 41.0.!!.!!
5 18 ms 19 ms 19 ms 41.0.!!.!!
6 18 ms 31 ms 21 ms 41.0.!!.!!
7 23 ms 33 ms 22 ms 41.0.!!.!!
8 19 ms 19 ms 21 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.253.109]
9 135 ms 136 ms 146 ms mweb-gw.telkom-ipnet.co.za [196.25.8.250]
10 113 ms 114 ms 120 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]
11 104 ms 111 ms 104 ms tengig-0-0-0-92.vic-ipc-1.mweb.co.za [196.22.189.17]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

p.s. I'm currently doing this from work, hence me blocking out my works IP's and stuff, but this happens from any location.
 
hammell said:
I wouldn't rely too much on pings/icmp. Most routers these days are not configured to reply to pings. If you have opened a port and are sure forwarding is correctly set up you can test this by telnet. From a command prompt:

telnet X.X.X.X 3389

If the prompt goes blank, that means that the port is opened (substitute 3389 for anything). If the prompt just sits there, it's not open.
Click to expand...

Machine @ work doesn't have Telnet installed - give me 15 mins to add it quick, will get back to you then :)
 
XperiAnce said:
Machine @ work doesn't have Telnet installed - give me 15 mins to add it quick, will get back to you then :)
Click to expand...

Results as below. I'm 99.99% sure that I told my router to not accept Telnet commands though, as I know how vulnerable they can be.
Remember, when I went to bed that night, I could remote desktop into the machine fine. Woke up and could only remote desktop using the local address - been like that since.

C:\Users\Michael>telnet 41.135.!!.!! 3389
Connecting To 41.135.!!.!!...Could not open connection to the host, on port 3389
: Connect failed
 
I've never heard of or used Nmap, so for all I know I've gotten this completely wrong, but here's my results.

C:\Program Files\nmap-5.21-win32\nmap-5.21>nmap -sVC -O -T4 41.135.!!.!!

Starting Nmap 5.21 ( http://nmap.org ) at 2010-10-04 12:05 South Africa Standard
Time
Nmap scan report for 41-135-!!-!!.dsl.mweb.co.za (41.135.!!.!!)
Host is up (0.00011s latency).
Not shown: 999 filtered ports
PORT STATE SERVICE VERSION
80/tcp open http-proxy Squid webproxy 2.5.STABLE14
| http-open-proxy: Potentially OPEN proxy.
|_Methods supported: GET HEAD
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Device type: general purpose
Running: Linux 2.6.X
OS details: Linux 2.6.9 - 2.6.18

OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 57.19 seconds

C:\Program Files\nmap-5.21-win32\nmap-5.21>
 
Hmm. It's strange that it's suddenly stopped working. Afaik Mweb won't block any ports so it must be either the router or rdp service on the pc. What your telnet says to me is that 3389 is not open. I understand that you've turned telnet off, but that just means the default service. You can use telnet to check if any port is open by using it as specified.

I would check the status of the services on your router - perhaps reset them? Do you have more than one system at home?
 
C:\Program Files\nmap-5.21-win32\nmap-5.21>nmap -p3389 41.135.!!.!!

Starting Nmap 5.21 ( http://nmap.org ) at 2010-10-04 12:17 South Africa Standard
Time
Nmap scan report for 41-135-!!-!!.dsl.mweb.co.za (41.135.!!.!!)
Host is up (0.00s latency).
PORT STATE SERVICE
3389/tcp filtered ms-term-serv

Nmap done: 1 IP address (1 host up) scanned in 0.54 seconds

I'll double triple check the Services tonight when I'm at home, but I remember setting them up as forwarding port 3389 (TCP) to 192.168.0.28 - last time I checked (yesterday afternoon) it was exactly the same.
 
honestly, enable the logging on the router firewall...
 
Turned on logging on my Firewall, absolutely no reference for incoming connections on port 3389 (Because remote desktop can't find my IP Address, therefore can't make a connection) - I completely disabled my Firewall and reset my connection, still no luck.

I'm leaning more towards this not being a firewall issue, as I can still play online via Xbox Live (which runs through my firewall on a variety of Ports) as well as download Torrents (Open Source Software and PDF's of free poetry). Also tripple checked my Services and Firewall rules on my router, set up 100% - also upgraded to the latest DG834GT Firmware, again no luck.
 
XperiAnce said:
Turned on logging on my Firewall, absolutely no reference for incoming connections on port 3389 (Because remote desktop can't find my IP Address, therefore can't make a connection) - I completely disabled my Firewall and reset my connection, still no luck.

I'm leaning more towards this not being a firewall issue, as I can still play online via Xbox Live (which runs through my firewall on a variety of Ports) as well as download Torrents (Open Source Software and PDF's of free poetry). Also tripple checked my Services and Firewall rules on my router, set up 100% - also upgraded to the latest DG834GT Firmware, again no luck.
Click to expand...

ok, just to double check, you have turned on logging for all rules? (dropped and accepted??)
if so, and there is no port 3389 reference, the traffic is not reaching your modem/router.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X