NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
wndr3400 After new spectrum service install i can not RDP, remote into or ping from outside.
I know this model is a bit older but it was working just fine and still is to a certain degree. WNCR3400. One day i have one service provider with one static IP and everything is working fine. Nex...
> [...] Then I in a different part of the world attempted to ping his
> that IP and could not [...]As usual, an actual error message would be more helpful than "could
not", but this would suggest (to me, at least) that the WNDR3400v2configuration is not your problem.
> [...] Technicolor TC8717T [...]
That is a modem+router.
> [...] which I did log into today with the default username and
> password."log into" using a web browser? Address/URL?
I'd start looking to see how it's configured. I have never touched a
TC8717T, and I haven't dealt with a block of addresses for decades, and
that was on a DSL connection, so my ability to advise on that stuff may
be very weak.
> wndr3400 [...]
> [...] WNCR3400. [...]
WNDR3400[v1]? WNDR3400v2? WNDR3400v3? Firmware version?
> [...] i get spectrum cable service with a static IP and my rdp port
> forward stops working, i can't get a ping responce from it when that is
> enabled. [...]
You "can't get a ping responce from" _what_? To what? What,
exactly, are you doing? What, exactly, happens when you do it? As
usual, showing actual actions with their actual results (error messages,
LED indicators, ...) can be more helpful than vague descriptions or
interpretations.
What's the actual port-forwarding rule? Copy+paste is your friend.
Note that "ping" and Microsoft Remote Desktop have very little to do
with each other.
> [...] I changed the setting in the netgear to reflect the gateway IP I
> was provided and gave the netgear my first usable IP. [...]
Which "the setting in the netgear"? What, exactly, in "the netgear"
did you give what, exactly? What, exactly, does "my first usable IP"
mean to you?
> [...] Called them [...]
Spectrum?
> [...] mutiples times to confirm their equipment is in bridge mode.
What, exactly, is "their equipment"? We don't need their help to
determine that. What is the WAN/Internet IP address of your "the
netgear"?
If you're worried about revealing your public IP address, then report
at least the first two octets ("a.b" out of "a.b.c.d") for any worrisome
IP Address.
> [...] I can login to the netgear inside the network and i can rdp to
> my server inside the network. [...]
How, exactly? Are you specifying the LAN IP address of your "my
server", or what? (And what is that address?) What happens if you
specify the WAN/Internet IP address (and the external port number, if
different) of your "the netgear" from a system on your LAN?
> [...] All that changed was the IP's and the equipment that sits in
> front of the netgear.
All that changed was a bunch of important stuff. That's probably
enough. Sadly, the non-psychics in your audience may not be able to
guess what your new "the equipment that sits in front of the netgear"
might be, or how it's configured, or what the port-forwarding rules on
"the netgear" might be, or what the IP address of your "my server" might
be, or what the WAN/Internet address of your "the netgear" might be.
All of which might be interesting.
The usual problems with this stuff are:
1. Wrong external IP address (different from the port-forwarding
router's WAN/Internet IP address). (An intermediate NAT router, for
example, could cause this.)
2. Bad port-forwarding rule (wrong port(s), wrong target address --
including a wandering target).
3. Server not listening on the port-forwarding target system.
4. External influences: ISP blocking, other firewalls, ...
My quick guess, based on incomplete information, is "1".