Networking issues... it is me or shaw? Guru's chime in :)

[Thaco]

Hey, anybody else have this issue? i can seem to send and receive pings from within shaw's network, my friends connected to my vnc, from within shaw's network, but i can not ping/tracert or vnc from outside shaw's network

Here's a tracert from outside shaw's network to my pc

Executing 'traceroute -m 30 -q 1 -w 3 -f 3 .107'

traceroute to .107 (.107), 30 hops max, 40 byte packets
3 rtr-border1-p2p-core1.slac.stanford.edu (134.79.252.133) 0.787 ms
4 192.68.191.245 (192.68.191.245) 0.540 ms
5 sunnsdn2-slacmr1.es.net (134.55.217.2) 0.675 ms
6 sunncr1-sunnsdn2.es.net (134.55.209.98) 1.073 ms
7 denvcr1-sunncr1.es.net (134.55.220.49) 51.503 ms
8 chiccr1-denvcr1.es.net (134.55.209.46) 51.785 ms
9 chislsdn1-chicr1.es.net (134.55.207.34) 51.711 ms
10 eqxchirt1-chislsdn1.es.net (134.55.218.81) 53.075 ms
11 198.125.140.238 (198.125.140.238) 53.120 ms
12 ae-11-51.car1.Chicago1.Level3.net (4.68.101.2) 53.969 ms
13 BIG-PIPE-IN.car1.Chicago1.Level3.net (4.79.208.150) 54.024 ms
14 rc2nr-pos14-0.wp.shawcable.net (66.163.76.173) 72.042 ms
15 rc1so-pos14-0-0.cg.shawcable.net (66.163.77.157) 104.732 ms
16 rd1so-ge6-0.cg.shawcable.net (66.163.71.130) 104.520 ms
17 dx1no-g1.cg.shawcable.net (64.59.142.105) 105.293 ms
18 *
19 *
20 *
21 *
22 *
23 *
24 *
25 *
26 *
27 *
28 *
29 *
30 *

I've done this a bunch of times from different places and it fails every time on the same one.

I also did a tracert from my home pc to an outside Ip and it only made it to the hop is 192.168.1.1 and then timed out.

I also can not ping my home pc, or VNC in, from a system outside of shaw's network.

I think this is shaw's fault, but i really can't tell, i don't know that much about networking.

[Chris Ng]

your router's hardware firewall or a firewall installed on your pc blocking outside traffic

[Thaco]

why would my router be blocking all inbound traffic?

I do not have any software firewalls and windows firewall is disabled.

[nos_efx]

Your router is a firewall, check you router settings.

[GQBalla]

easy fix - but kinda worthless especially if you have a lot of settings on your router ( mac filtering, open ports, etc)

hit the reset button on yourrouter.

also to troubleshoot this properly was it always like this?
did you make any configuration changes recently?
new router?

it does sound like your router is blockin all outside traffic
go into your router and take a look at the firewall settings.

[forced14]

What happens when you connect your PC directly to your shaw connection? Might want to get a software firewall before trying, or enable windows firewall.

If it is successful at this point, then all problems point to your router. If it still does not work, then need to keep investigating.

I searched up what TCP port VNC uses and found it is TCP/5900. Are you able to telnet to your IP address on that port from different providers?

It is also possible that Shaw is blocking ICMP at certain parts in its network.

One other suggestion would be to run a program like Wireshark / Ethereal on your machine to see if you are getting any responses and your machine is shutting them down.

[Thaco]

i got it figured out, i can now tracert and ping myself, there was a default setting in my router that was turned off that allowed pings to come in, but my remote desktop still wont connect...

[snipa_mini85]

You need to forward the remote desktop port to you computer's IP in the router's configuration.

[Thaco]

Originally posted by snipa_mini85
You need to forward the remote desktop port to you computer's IP in the router's configuration.

done, in 3 different places.

[snipa_mini85]

Originally posted by Thaco
done, in 3 different places.

Which OS do you have?

[Thaco]

vista, firewall completely disabled.

[whoatemyling]

Which port did you forward?

RDP is default to TCP 3389

thus your port forwarding rule should look something like this:

-------------------------------------------------------
Protocol:
TCP

External IP/Subnet
1.1.1.0/24

External Port
3389

Internal Port
3389

Internal Destination
192.168.1.2

----------------------------------------------------------

[Thaco]

yeah, i forwarded 3389.


I found a setting in my router that blocked pings, i turned that off so now i can ping and tracert myself, but i'm still having issues connecting to Remote Desktop... i found out one thing that was an issue, and that is that Vista home does not support remote desktop, so i formatted and went to XP pro, RDP still will not work, i haven't tried VNC yet, I'll try that tomorrow, hopefully it works.....

[sputnik]

For XP Pro you might have to turn on RDP.

Right click My Computer -> Properties -> Remote

[Thaco]

Originally posted by sputnik
For XP Pro you might have to turn on RDP.

Right click My Computer -> Properties -> Remote

yeah, i have it turned on, my friend was able to connect last night, but i cant get in today... could even be my power settings, it may have gone in to standby or something, not sure, haven't really checked any settings since the format.

[sputnik]

Get in from where?

If you are using a computer connected to the same router you will have to RDP to the internal address.

[sabad66]

try connecting to the net straight to the shaw modem and then try remote desktop. If it works then its your router if not then its your computer and/or shaw

[whoatemyling]

see if you are able to telnet from where you are back home on port 3389

telnet xx.xx.xx.xx 3389


If you are able to connect then your firewall rules (port forwarding) is working.

I honestly don't think going to VNC is going to resolve your issue.

[Thaco]

Ugg, thanks for the suggestions guys, i'm trying to RDP or VNC from work to home, i just don't get it.. i have ports 3389 (RDP) and 5900 (VNC) forwarded at home, no dice, i even put my pc at home in DMZ on my router, still no dice... and connecting straight to my modem isn't an option, unless i want to unhook my pc and move the entire thing in to another room... but thanks for the suggestion... i just don't get it, my friend can connect via RDP and VNC, but i cant get there from work... I'm thinking it is work related or something.

also, the telnet doesn't work

[GQBalla]

possibly work related have you tried to ssh? port 22 i believe