• March 28, 2024, 04:51:46 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 2 [3] 4 5

Author Topic: 413 - Request Entity Too Large  (Read 19954 times)

CaseyJanke

  • Level 2 Member
  • **
  • Posts: 33
Re: 413 - Request Entity Too Large
« Reply #30 on: February 09, 2017, 09:07:32 PM »

Yes. All the cameras are above 200 (203 through 225). Outside the DHCP range.

I turned off the upnp. Thanks.

I guess I will go onsite and try the factory reset thing. Luckily there are only a few things to configure.

Logged

RYAT3

  • Level 10 Member
  • *****
  • Posts: 2254
Re: 413 - Request Entity Too Large
« Reply #31 on: February 09, 2017, 09:18:03 PM »

Is this a new setup?  If not - I'm not sure if I missed previously in a post - what where you using before and was it working completely?  If there was - why the switch out?  (Just curious.... it sounds like what you are doing should work with this modem).

Logged

CaseyJanke

  • Level 2 Member
  • **
  • Posts: 33
Re: 413 - Request Entity Too Large
« Reply #32 on: February 09, 2017, 09:31:23 PM »

For the most part everything was working fine on an RV110w router. EXCEPT the fact that apparently the RV Series routers have an issue where the assign ip phones the same SIP port, which causes issues. The DIR-655 is on the VOIP providers list of approved routers, hence the move to this router. I do hope it will resolve the issue. It's just that it has now caused another, where I can't port forward.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 413 - Request Entity Too Large
« Reply #33 on: February 10, 2017, 06:58:11 AM »

Let us know how it goes when you get on site and factory reset the router with one camera with the PC. I would try using default 192.168.0.1 first as a test. If you can get PF to work here, you could try changing to .1.1 and see.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

CaseyJanke

  • Level 2 Member
  • **
  • Posts: 33
Re: 413 - Request Entity Too Large
« Reply #34 on: February 10, 2017, 08:17:23 PM »

Ok, so here is some follow up info.

I went onsite and reset the router to factory. Logged in 0.1 and for fun added a port forward. it worked fine. I then changed subnet to 1.1 and restarted. Went to port forward and the one I entered was gone. Which is fine because it changed subnets so there was no 0.152. So then I tried adding the 1.152:81 forward and got the 413 message again. Ahhh! I restarted though and it was there (I saw this in a post that this might happen). When I go in and try to add another, yup, I get the message 413 again. Tried to reboot to see if it showed up and it didn't. Tried adding it again and get the 413 message.

I was hoping this would be a good replacement for my RV series which dont' play well with VOIP, but I can't deal with this wonkiness. So, if anyone has any suggestions on a router that will work well with VOIP and is inexpensive, easy to configure and solid, suggestions are welcome. RV series is out due to sip port assigment issues. DIR-655 is out due to some "funny" things which I have to work too hard to finally make work, DSR-500n seems to be out as it shoudl have just connected to the internet without an issue (the RV110W did and the DIR-655 did).

So I'm looking for a descent basic router that can handle 60/5 and 100/10 and supports VOIp and port forwarding. This would be for many of my clients. For the hard core ones who want all teh security and bells and whistles I guess I'm looking at Cisco Meraki or Dell Sonicwall.

Thanks for all the help with this.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 413 - Request Entity Too Large
« Reply #35 on: February 11, 2017, 12:32:18 PM »

I would try using the .0.1 DHCP pool instead of .1.1. Seems like if you got it to work on .0.1, then it should work all around for this pool address.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

CaseyJanke

  • Level 2 Member
  • **
  • Posts: 33
Re: 413 - Request Entity Too Large
« Reply #36 on: February 12, 2017, 07:09:04 AM »

Thanks. I thought about that .... until ... I realized that I would have to manually change the ip address on:
1 Server
6 Printers
24 ip cameras

That's when I decided that I shouldn't have to be doing all this dorking around and troubleshooting, the equipment should work and if it doesn't or is THIS quirky, I can't afford to put it in any of my clients environments. I may still go with D-Link (different model) down the road, but I got my hands on a Netgear R6220 and heading down there this morning to replace it.

D-Link needs to get itself into stores like Best Buy and Staples. I went there for a new router the other day and both stores were pretty much exclusively Netgear and a Linksys or 2 and same for Staples.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 413 - Request Entity Too Large
« Reply #37 on: February 12, 2017, 12:12:07 PM »

I find D-Link routers in Office Max/Depot.

Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

CaseyJanke

  • Level 2 Member
  • **
  • Posts: 33
Re: 413 - Request Entity Too Large
« Reply #38 on: February 13, 2017, 07:41:15 AM »

Thanks. The Office Max that was 15 minutes from me closed. So now the closest one is 30 minutes. So I guess I'm kind of in test mode right now. I replaced the DIR-655 that I was having problems with with that netgear R6220. So we will see how that goes this week. I also found someone selling 3 DIR-655's on ebay and got them for like $20. So when they arrive I will have the new one I have and the 3 old ones from ebay to dork around with and test. If those work I will replace some of the cisco's rv110w's with those, otherwise, if that R6220 works well at my one client I might stick with that for my smaller clients.

Ironically in the lower end market (aka, "not security appliance" area) I think the consumer products might be better than some of the "business" routers because with all the streaming and gaming, they have had to make the consumer ones perform just as fast if not faster than the business ones.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 413 - Request Entity Too Large
« Reply #39 on: February 13, 2017, 07:52:53 AM »

What Rev models are the ones from ebay?
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

CaseyJanke

  • Level 2 Member
  • **
  • Posts: 33
Re: 413 - Request Entity Too Large
« Reply #40 on: February 13, 2017, 09:03:24 AM »

Unfortunately they didn't list it in the ad. Even if you could tell the hardware rev by UPC, I'm not sure if they used teh real UPC or just pulled the specs and that info from Amazon. So will have to wait until I receive them.

The one that I brought back to my office from the client is Hardware: C2 and Firmware: 3.02.

Although I can seem to get it to throw the 413 error now and then, a reboot seems to fix it so I can enter more port forwards since I have 4 of them in there now as a test. And I am using the 192.168.1.1 subnet.

Sooooo, maybe in the end, my normal practice is to dive right into configuring a router and the last step is to update the firmware. I guess I will change my process to update firmware first, then factory reset, then configure. After that I will only upgrade firmware if there is an issue that new firmware addresses and realize that chances are I will have to factory reset after and reconfigure it all again (as in don't even export and import the old config).

I'm going to set QOS settings on this now for my phone system (8x8.com) and see how that goes. Then test the others out when they arrive. Although I'm still kind of leaning that for anything new, I will go with the NG R6220. There were just no quirks with it at all during the setup and I'm not sure if teh DIR-655 is even going to continue to be made.

Thanks again.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 413 - Request Entity Too Large
« Reply #41 on: February 13, 2017, 09:39:33 AM »

Im hoping it maybe Rev B. BLUE LED is Rev A and B, Green is C only.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

CaseyJanke

  • Level 2 Member
  • **
  • Posts: 33
Re: 413 - Request Entity Too Large
« Reply #42 on: February 19, 2017, 01:02:02 PM »

The routers I bought from Ebay won't arrive till tomorrow. So no update on what REv's they are. However, just some more information since I have been using this Rev C one in my home/office. Ironically my home office is probably a more taxing on a router than any of the businesses I take care of as I have two teen age kids who are always either gaming or streaming netflix, along with my wife streaming netflix and often myself as well.

Overall the performance seems great. How is that measured? My son is yelling at his computer while playing League of Legends and saying "This stupid LAG!!!". So performance wise we are good.

I was dorking around today and wanted to make 2 changes. I wanted to name the router mytechco and I wanted to name the local domain mytechco.com

I did that and hit save and instantly got the error 413 - Request Entity Too Large. I instantly rebooted the router and made the changes again and hit save and it worked.

So my theory (probably wrong, but what the heck) is that when the router has been running for some time, I assume there is memory in it that is being used and over time it is used effectively to cache things (call them what you will, routes, dns resolutions, or whatever else a router might store in memory). At that time, if you try and make a change and there is no more capacity to temporarily store the changes, it throws this error. As soon as you restart (I assume clearing out the memory) you can now quickly make and save those changes before the memory is all used up.

Again, could be totally off base, but my only guess at this point.

Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 413 - Request Entity Too Large
« Reply #43 on: February 19, 2017, 04:04:32 PM »

I was told the following:
"-Not easily reproduced.
-Resolved when using a different browser.
-"413 Request Entity too large" is a HTTP browser error.

It might be a browser cache issue or HTTP code conflict between client and server. I highly doubt it is a router firmware issue."
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

CaseyJanke

  • Level 2 Member
  • **
  • Posts: 33
Re: 413 - Request Entity Too Large
« Reply #44 on: February 19, 2017, 05:58:03 PM »

Thanks! I'm sticking with my theory though. Here's why
1. For us to use a web browser to connect to the router, it HAS to have some kind of web server on it. Obviously it needs to be a very light weight and low memory usages server. If you search the web for the 413 error you are often directed to people trying to upload large files to a web server. Often they complain it is a nginx web server.
2. Nginx has a Linux version.
3. I'm guessing the router software is linux based and running nginx as its web server.
4. I'm guessing over time that there isn't enough memory to make configuration changes and a reboot clears up some memory and therefor after a reboot you can then make changes without getting the error.

This morning I made changes and got the error using Chrome. I rebooted the router and made the changes without the error. Still using Chrome and not clearing the cache or anything.

Now that the router has been running all day, I figured I would try to make another change, a simple port forward, and sure enough it threw the error again. I'm guessing if I reboot I cold then make the change.

This may or may not be the issue, but it seems logical to me and I hate the random. It has to be explainable and it's the best I can come up with.
Logged
Pages: 1 2 [3] 4 5