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. Next day 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. I can't remote into the router from outside my network. Internet works fine and my VOIP phone system is working fine. I changed the setting in the netgear to reflect the gateway IP I was provided and gave the netgear my first usable IP. Set up their suggested DNS IP's. Called them mutiples times to confirm their equipment is in bridge mode. I can login to the netgear inside the network and i can rdp to my server inside the network. Can't from outside. All that changed was the IP's and the equipment that sits in front of the netgear.
> [...] 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.
13 Replies
> 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".Wow, feels bad, Charlie Brown walk.
Let me be more in depth for you. WNDR3400v2
PING- Equipment involved Spectrum Arris modem/router (i do not know the exact model number as I have not been on site) that is set in bridge mode that has a gateway public IP from spectrum. NetGear WNDR3400v2 set for static IP with first usable public IP, (provided by spectrum) subnet mask, gateway IP (referencing spectrums gateway IP they supplied me (which i can ping from outside of the domain, a computer in my office in another city)
I can't ping the public IP from Spectrum (first usable IP) from anywhere outside of my network. From any computer outside of that LAN to that WAN IP. Pings from outside time out from CMD. There are no errors to show. The setting in the NetGear router that has to do with responding to ping it enabled. * I'm fully aware that ping and rpd are completely separate * It’s odd that all of this works before Spectrum service and none of it works after service.
RDP- I set a rule in port forwards called RDP with and alternate port referenced that my server is set to listen on for RDP requests. This rule says to use TCP and to forward :XXXX to my servers internal (private) IP:XXXX address. My server is most certainly listening on the port for RDP. I would copy and paste it for you however I cannot get into the NetGear router nor my server because RDP and the remote management (this feature is also turned on) feature built into the NetGear router are not working. I will have to drive out and get eyes on next with or try to get someone to do a go to with me out at that location.
Spectrum and IP's - This location signed up for this service and did not include me in the discussion. I was called on the turn up date and forwarded an email with a block of IP addresses from Spectrum which included;
Network:71.66.x.x
Gateway: 71.66.x.x
Useable: 71.66.x.x
Broadcast:71.66.x.x
Size: /30
Subnet:255.255.255.252
TWC DNS1:209.18.x.x
TWC DNS2:209.18.x.x
Spectrums equipment gets the "gateway" IP which I can ping
I had someone onsite set the NetGear Router, under "internet setup" as "use static ip" with "Usable" IP from spectrum as the IP address, IP "Subnet Mask" as "Subnet" IP provided by Spectrum, "Gateway IP address" as "Gateway" IP and DNS server IP's provided by Spectrum as DNS IP's
THEM - YES I had the people on site call SPECTRUM to confirm their equipment (and Arris cable modem/router) was in bridge mode and not double NATing with the NETGEAR. I don't know the spectrum equipment's exact model number as of yet. I will have to drive out or do a go to on a device inside their domain. The NetGear is apparently (I haven't gotten eyes on) set with 71.66.x.x as WAN (usable IP from spectrum)
Inside the building (LAN) I've had someone on site log into the NetGear router using its internal IP address....works. I've had that same person remote into the server in question using the internal IP + port and using the server name....works. The address scheme of the LAN is default of 192.168.x.x
I'm sorry that it's short on the detailed info as I do not really have a reliable person onsite. I am going to try and make it out there next week. The RDP is not critical and seeing how the internet is up and running at full speed with current settings it hasn't been a rush for me.
When sitting on the LAN the user can use the WAN IP of 71.66.x.x:8080 (usable IP assigned to the NetGear router provided by Spectrum) to access the "remote management" of the router. I cannot from my office in another city.
I will try to obtain more info......sorry
Today i was able to get on a goto meeting with someone on site and the NetGear router is configured correctly with the proper IP's from Spectrum. The port forward rule is configured correctly and we are seeing the port forward attempts hitting the log of the netgear. I still can not ping, remote manage (using the built-in feature) the netgear, nor RDP to the my internal server from outside the LAN. All this this can be done within the LAN. I can ping the spectum modem from outside as well.
Firmware version: v1.0.0.54_1.0.82