++ ATOT official NEF thread part IV ++

[MotF Bane]

My uncle is having computer problems again.

 

[Rubycon]

pain in the ass. I hate moving.

Sounds like you're doing it wrong.

 

[MotF Bane]

Fucking Verizon. I can't get into my own router.

 

[MotF Bane]

Those goddamned idiots decided to roll back from Ethernet to coax for FIOS, and in doing so, annihilated the network I'd carefully set up, and stuck with me with a gigantic steaming pile of shit router from the 90's.

 

[MotF Bane]

Anyways, the default password isn't what they said it is.

 

[MotF Bane]

So I need to call Verizon, find out what the fuck they set the default password to, inevitably find out they can't help me, then who knows where the fuck this is going to go.

 

[MotF Bane]

And the fact that there are so many responses to questions about my router online asking for the default password proves what a fucking mess Verizon made of it.

 

[Rubycon]

Do a hard reset and try it.

You think your day with the computer is bad eh?

Think again!

 

[MotF Bane]

Progress. I'm posting this from my desktop... via my laptop.

 

[MotF Bane]

I did a hard reset, finally got into the router, I have no idea what the Verizon tech ever must've set the default password as before.

Set up port forwarding on 3389... and online check sites still say 3389 is closed. My interpretation - Verizon has 3389 blocked on their end, which will end this whole adventure.

 

[MotF Bane]

I've opened RDP for my desktop and laptop, I'm going to close the laptop, since it isn't secure.

The desktop will accept connections from any RDP who has my password. The laptop has no password at all.

 

[MotF Bane]

Now... how do I open this fucking port?

 

[MotF Bane]

Also, I believe the computers in my house shuffle their 192.168 IP's on a regular basis, but the router requires me to specifically target one IP.

 

[Rubycon]

Never heard of an ISP blocking RDP traffic.
Create a rule allowing TCP traffic on port 3389. Depending on the router you may have to create a custom service (if it's not listed in preconfigured service table). Then create a rule using this service and forward to a local (NAT) IP. You can use IPCONFIG and use that IP address on the target machine if you have a DHCP scope provided by a server or the router itself. Alternatively you can specify a static local IP so you don't have to worry about it changing.

 

[MotF Bane]

Can somebody test something for me, involving RDP?

 

[Rubycon]

I can just need an IP. If it works I should see a logon screen.

 

[MotF Bane]

Never heard of an ISP blocking RDP traffic.
Create a rule allowing TCP traffic on port 3389. Depending on the router you may have to create a custom service (if it's not listed in preconfigured service table). Then create a rule using this service and forward to a local (NAT) IP. You can use IPCONFIG and use that IP address on the target machine if you have a DHCP scope provided by a server or the router itself. Alternatively you can specify a static local IP so you don't have to worry about it changing.

With Verizon, nothing would surprise me much anymore.

I tried to add a rule for 192.168.1.x and couldn't, I had to specify 192.168.1.4 (my primary computer's current address). It was not preconfig, so I told it custom, clear TCP/UDP 3389.

IPconfig was unnecessary, all the computers are named, and the router showed me their names and internal addresses.

Static local IP, as in fixed 192.168.1.** numbers? I'll look into that.

 

[MotF Bane]

I can just need an IP. If it works I should see a logon screen.

173.76.167.42

I don't know how to tell it which computer to target, but I've put my laptop into DMZ.

 

[Rubycon]

Those are DNS names and ASSUMES that DNS works both ways. This is not always reliable. If you want reliability you must use a static IP for target clients and (if your DHCP server supports it) create an exclusion range for these ips so they cannot be assigned by the DHCP server which will create the dreaded duplicate IP conflict.

 

[Rubycon]

That IP answers an RDP request.
Oh yeah DMZ not so good! Make sure you have at least some firewall running on it!

 

[MotF Bane]

There's a static NAT page, trying to figure out what that is.

 

[MotF Bane]

That IP answers an RDP request.
Oh yeah DMZ not so good! Make sure you have at least some firewall running on it!

Windows firewall, no password. It's my laptop, I keep nothing on it that I would be upset to have compromised.

Thanks for checking though. If it's answering, that means VZ isn't killing me.

 

[Rubycon]

Does it have a help tab? Usually that gives some info on it.

By default a computer with no password won't allow logon interactively (i.e. RDP) so that's relatively safe.

 

[MotF Bane]

Just closed the DMZ.

 

[MotF Bane]

Does it have a help tab? Usually that gives some info on it.

By default a computer with no password won't allow logon interactively (i.e. RDP) so that's relatively safe.

No help tab given by router for anything really.

By default no longer applies; the laptop has been told to accept remote access requests from all computers. Again, that's just a temporary measure, I'll close it down later.