[WXC/VFX] Can't get RDC working

Forums › One New Zealand (including Vodafone, WxC, Farmside) › [WXC/VFX] Can't get RDC working

gchiu

1211 posts

Uber Geek

Trusted

#13339 5-May-2007 00:59

I connected up xnet to a business that is running Woosh wireless as the latter is just too slow for RDC.
Now I can connect up RDC using Woosh slowly .. but I can't get RDC working with xnet. They tell me they're not blocking any ports. I can't even ping the static IP I ordered either .. though I'm not sure that is relevant.

I'm using an old Nokia MW1122 and the firewall table is blank. I have incoming UDP and TCP on 3389 being NAT'd to the PC running terminal services.

Suggestions?

freitasm

BDFL - Memuneh
79270 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#69575 5-May-2007 09:33

Try the free version of Logmein.

nic.wise

333 posts

Ultimate Geek

Trusted

#69588 5-May-2007 11:33

gchiu: I connected up xnet to a business that is running Woosh wireless as the latter is just too slow for RDC.
Now I can connect up RDC using Woosh slowly .. but I can't get RDC working with xnet. They tell me they're not blocking any ports. I can't even ping the static IP I ordered either .. though I'm not sure that is relevant.

I'm using an old Nokia MW1122 and the firewall table is blank. I have incoming UDP and TCP on 3389 being NAT'd to the PC running terminal services.

Suggestions?

If you can't ping it, it MAY be a problem. Try tracert to it (and post it here if you like), and also telnet 3389 - if it connects, you are good

I've never had a problem with RDC over ADSL..... :)

Can you find out what the current IP of the remote router is? ie, not take it for granted that it has the static ip?

Nic Wise - fastchicken.co.nz

gchiu

1211 posts

Uber Geek

Trusted

#69596 5-May-2007 12:57

Here's the tracert

Tracing route to ip-58-28-159-30.ubs-dsl.xnet.co.nz [58.28.159.30]

over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.1.254
2     1 ms     1 ms     1 ms 192.168.0.1
3    50 ms    50 ms    49 ms 222-155-128-1.jetstream.xtra.co.nz [222.155.128.1]
4   184 ms    80 ms   158 ms fid-dom.aksw7.global-gateway.net.nz [202.50.245.194]
5    65 ms    59 ms    57 ms v282.aksw7.global-gateway.net.nz [202.50.245.193]
6    57 ms    59 ms    56 ms wxc-dom.aksw7.global-gateway.net.nz [203.96.116.54]
7    58 ms    73 ms    57 ms ip-58-28-8-6.wxnz.net [58.28.8.6]
8    58 ms    57 ms    58 ms ge-0-0-akl-dsl02.wxnz.net [58.28.13.51]
9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12

The ip address is correct ... well, according to www.whatismyip.com

Telnet fails unable to open connection on port 3389

nic.wise

333 posts

Ultimate Geek

Trusted

#69599 5-May-2007 13:42

gchiu: Here's the tracert

Tracing route to ip-58-28-159-30.ubs-dsl.xnet.co.nz [58.28.159.30]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 1 ms 1 ms 1 ms 192.168.0.1
3 50 ms 50 ms 49 ms 222-155-128-1.jetstream.xtra.co.nz [222.155.128.1]
4 184 ms 80 ms 158 ms fid-dom.aksw7.global-gateway.net.nz [202.50.245.194]
5 65 ms 59 ms 57 ms v282.aksw7.global-gateway.net.nz [202.50.245.193]
6 57 ms 59 ms 56 ms wxc-dom.aksw7.global-gateway.net.nz [203.96.116.54]
7 58 ms 73 ms 57 ms ip-58-28-8-6.wxnz.net [58.28.8.6]
8 58 ms 57 ms 58 ms ge-0-0-akl-dsl02.wxnz.net [58.28.13.51]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12

The ip address is correct ... well, according to www.whatismyip.com

Telnet fails unable to open connection on port 3389

The only thing I can think of is that the router at the other end is not responding to ICMP and the port isn't open. Otherwise, I guess call wxc :(

Nic Wise - fastchicken.co.nz

Wendy

59 posts

Master Geek

Trusted

#69619 5-May-2007 16:51

AFAIK the M1122 routers blocked ICMP by default. The trace posted gets to the hop before the customer so it's at that end where the trace dies.

As for port 3389, I'm not sure why it's not working for you. The port definitely isn't blocked anywhere on the network so there's no reason for it not to work, and I use it myself so I know it does work. :) I would give the helpdesk a call and see if someone there has any ideas. I've not played with setting up pinholes on the M1122's so I'm not sure how any of that works but the guys will probably have the manual and be able to troubleshoot it with you.

nic.wise

333 posts

Ultimate Geek

Trusted

#69622 5-May-2007 17:16

Wendy: AFAIK the M1122 routers blocked ICMP by default. The trace posted gets to the hop before the customer so it's at that end where the trace dies.

As for port 3389, I'm not sure why it's not working for you. The port definitely isn't blocked anywhere on the network so there's no reason for it not to work, and I use it myself so I know it does work. :) I would give the helpdesk a call and see if someone there has any ideas. I've not played with setting up pinholes on the M1122's so I'm not sure how any of that works but the guys will probably have the manual and be able to troubleshoot it with you.

Sorry if this sounds mean, but isn't using a M1122 like wondering why Doom3 doesn't work on win3.11? Or is the M1122 still considered a good modem? I thought Telecom et al stopped selling/using them ages ago...?

(of course, it's a LONG time since I used one, so I may be totally wrong - they WERE good back then.....)

Nic Wise - fastchicken.co.nz

Wendy

59 posts

Master Geek

Trusted

#69632 5-May-2007 18:40

Sorry if this sounds mean, but isn't using a M1122 like wondering why Doom3 doesn't work on win3.11? Or is the M1122 still considered a good modem? I thought Telecom et al stopped selling/using them ages ago...?

(of course, it's a LONG time since I used one, so I may be totally wrong - they WERE good back then.....)

Nokia haven't made them for a long time but they were a very reliable router and still are. We found that back in October/November when Telecom removed copper rate limits from lines and customers started experiencing dropouts that the M1122 was one of the more stable routers and handled some pretty awful line conditions really well.

If we didn't have a Cisco for our home router we'd still be using an M1122, it's still our home backup router. :)

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

grant_k

3539 posts

Uber Geek

Trusted

#69645 5-May-2007 21:14

gchiu: I'm using an old Nokia MW1122 and the firewall table is blank. I have incoming UDP and TCP on 3389 being NAT'd to the PC running terminal services.

Suggestions?

Until about 2 years ago, I used to have a pair of M1122s (same as yours, but without wireless). The firmware was buggy and I found that if I used VoIP for more than an hour after restarting the M1122, it would lock up solid, needing a power-on-reset to get it going again. There were also other issues my kids experienced with port forwarding that didn't work properly.

The MW1122 was a good router in its day, but I think you are best advised to go and buy something that is up-to-date. I have had a good run with 3Com and ZyXEL. Mauricio and Brad have had good experiences with Belkin. For heaven's sake DON'T buy a D-Link!

I think you will find that your problem will just go away with an up-to-date ADSL router from one of the recommended brands above. That's certainly been my experience.

One more thing... As Wendy has stated above, I'm pretty sure that response to ICMP requests (PING) was disabled by default in the MW1122. Have a look through the setup screens and you will probably find somewhere to enable it. Failing that, use TELNET to get to the CLI and you will be able to enable it from there.

Ooohh, CLI... That brings back bad memories of the time both of my newly purchased M1122s lost the contents of their flash at around 3 months after purchase. I had to use the CLI to load a new Boot Image via the serial port which took ages. See, I told you the Nokia Mx1122 series were dodgy

I hope that helps.

Cheers,
Grant.

aw

286 posts

Ultimate Geek

#69657 6-May-2007 00:50

Yeeeeeears ago I ran RDC and shortly afterwards a PPTP VPN service through a Nokia M1122 and it worked.

I still have access to that very router (I found it last week when cleaning up a server room!) so I can drag it out of mothballs and see if I can replicate the same thing here - at home I have a static IP with Xnet so it's a pretty similar scenario to yours.

I can get to the router this Monday - let me know if you want me to have a go at it.

Andrew

... edit: although I must admit getting a new router as Grant says would be much easier!

gchiu

1211 posts

Uber Geek

Trusted

#69659 6-May-2007 08:20

I suspect a problem with the NW1122 router as I can't even get http pin holing to work. I've got another M1122 I can try, and also a Linksys ADSL2 router that I will try today.

gchiu

1211 posts

Uber Geek

Trusted

#69660 6-May-2007 08:23

I just remembered another problem I had with all the MW1122s I've used. I could never get *any* 802.11g card to connect to it in b mode. Always could detect the wireless network .. but could never make the connection.

gchiu

1211 posts

Uber Geek

Trusted

#69671 6-May-2007 11:22

Don't really know what is going on .... I connected up this Linksys AG241-AU ASDL2 gateway with 4 port switch, and just couldn't get it to connect to Xnet.

So, I tried the M1122 I had. With this I can connect to xnet. Now I have the network connected via a switch which now connects to the M1122 ( the M1122 has 4 ethernet ports - only 10Mbs though ). If I try and nat http, it doesn't work unless the natted device is connected directly to the M1122. If it's connected to the switch instead, it won't work. PCs on the switch can see the PCs on the M1122.

So, looks like some type of networking issue. I guess I am going to have to replace the M1122/MW1122 with something else ...

gchiu

1211 posts

Uber Geek

Trusted

#69684 6-May-2007 13:49

I see Linksys has this ADSL2 gateway with VOIP (AG310) coming out soon. Perhaps I should wait for one of these?

gchiu

1211 posts

Uber Geek

Trusted

#71406 20-May-2007 18:10

I got an Linksys AG300 to replace the earlier ASL2 gateway device I tried.

I now have both Xnet and Woosh on the network.

I can now use RDC to access two of the PCs on the network, but with Woosh I can access three PCs. One of the PCs refuses my attempt to login using RDC on Xnet.

I'm stumped :(