Port forwarding on DIR 655

ChrisD. · 17 Sep 2011 at 11:57

Now that R30 is out on Virgins SuperBug, I've just switched on modem mode and connected up my 655.

Everything is working great on the 1.34WW firmware except I can't get RDP to work.

I've tried both Virtual Server and Application rules yet I still can't get RDP to work. I've added a .10 DHCP reserved address for my PC and I'm forwarding port 3389 to that port.

Am I missing something? It worked fine on the SuperBug. :confused:

ots3go · 17 Sep 2011 at 12:09

Is your PC definitely receiving the .10 IP address?

Forwarding TCP, UDP or both?

ChrisD. · 17 Sep 2011 at 12:12

Just TCP mate, I also tried with UDP but no difference (didn't expect any, since RDP is a TCP protocol).

PC isn't getting anything, it's being stopped at the router.

ots3go · 17 Sep 2011 at 12:15

Are you trying to remote to yourself from a different public IP address [remote out to come back in again] or internally trying to use your public IP address?

Also, I meant is your PC getting the .10 address from the DHCP, might be assigning something else in the pool even though you've set the reserved address.

ChrisD. · 17 Sep 2011 at 12:19

Internally initially, but I used my phone in 3G mode and that didn't work either. I've also just put the .10 IP into the DMZ and that's not worked either.

My WAN IP has changed, but the devices I'm using to connect with have been update to reflect this. I'm a bit confused.

ots3go · 17 Sep 2011 at 12:25

Only just moved the superhub over to the new modem mode myself, but I can now confirm it's letting my remote traffic through, so can probably rule that out.

No ACL's in place?

ChrisD. · 17 Sep 2011 at 12:28

ots3go said:
Only just moved the superhub over to the new modem mode myself, but I can now confirm it's letting my remote traffic through, so can probably rule that out.

No ACL's in place?

Nothing has changed on my PC. The only thing that has changed is modem mode on and plugging in the 655.

I didn't remove the rule from the SuperBug but NAT should be completely disabled on it.

I might flash the router with DDWRT and see if that solves it but I CBA setting everything up again.

ChrisD. · 17 Sep 2011 at 12:36

I'm an idiot.

It's a new network so Windows 7 defaulted it to Public, and not Home or Work. Changed to Home and it's working fine.

Dave85 · 17 Sep 2011 at 13:24

MilanoChris said:
I might flash the router with DDWRT and see if that solves it but I CBA setting everything up again.

Didnt think it was available for dir 655 due to chipset

ots3go · 17 Sep 2011 at 13:45

MilanoChris said:
I'm an idiot.

It's a new network so Windows 7 defaulted it to Public, and not Home or Work. Changed to Home and it's working fine.

Ha! Nice to know it's resolved at least.

.

ChrisD. · 17 Sep 2011 at 13:57

DAvE18 said:
Didnt think it was available for dir 655 due to chipset

I'm not sure, I just assumed.

ChrisD. · 17 Sep 2011 at 14:11

ots3go said:
Ha! Nice to know it's resolved at least. .

Indeed, I never thought it would be an OS issue as it worked before. Only after I set it to Home did I see the "new network" bit behind other open windows.