While I was working on the terminal server issues described previously, I checked the Netgear DEVG2020 router the ISP had provided to us. I have to say, the Netgear DEVG2020 is probably one of the most functional routers ever designed...
"What? I can't say that? Not passing packets on multiple connections, huh? It was causing the terminal server multiple connection issue? Really? Well, OK, let me try it again."
The Netgear DEVG2020. The router you need for security & performance...
"Not that either? Multiple VPN connections were being blocked as well? Oh, all multiple connections of certain types? Issues with business applications as well? Well..."
The Netgear DEVG2020. A router based on industry standards for internet connectivity and....
"Again, really?! Yeah, it has a customized firmware specific to each ISP? Completely unsuitable for business-critical internet access? Replaced as quickly as possible, huh? OK."
I'm sorry, it looks like I won't be writing a review for the Netgear DEVG2020 this week as it was apparently the cause of almost every networking issue I've seen for the past few weeks. It was replaced this past weekend by the ISP and all previously discussed issues have been fixed:
- Unable to connect to the terminal server twice in a row
- Unable to connect to the VPN twice in a row
- Extremely slow Windows desktop logins
- Business application connection issues
This explains why Microsoft was unable to see the packets for the second connections in the NetMon traces. Turns out it wasn't Sonicwall blocking the packets, it was the Netgear DEVG2020 that was dropping the connections.
Doing more internet research, it appears there are many cases of issues with this specific router from various ISP's globally. So the moral of the story is folks, if you happen to own a Netgear DEVG2020 router somewhere in your wide-area network, you may want to consider replacing it if at all possible.
![]() |
"What a piece of junk!" - Netgear DEVG2020 |
No comments:
Post a Comment