• April 25, 2024, 10:41:00 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 ... 5

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

CaseyJanke

  • Level 2 Member
  • **
  • Posts: 33
413 - Request Entity Too Large
« on: February 09, 2017, 04:45:35 PM »

I realize there are other posts on this, but one ended with the person buying a new router. Does anyone have any new insights? This is crazy that I just can't add a port forward without an error.

I was going to insert the images but when I click the insert image icon all i get is . Have no idea what I'm suppose to do with that.

Basically I am trying to add a port forward and when I hit save I get "412 - Request Entity Too Large". Tried it using Chrome Edge, IE, Firefox and remotely using Opera. All yield the same. I'm not onsite now and I'm afraid if I set it to factory defaults I won't be able to access it again as the computers may not pick up the new ip address (since I'm using 192.168.1.1 sub net and it uses 192.168.0.1 by default) and I don't think there is a way to factory reset it and keep remote management enabled.

Without the port forward, the router is useless to me. So I solved one problem by moving to this router and created a new problem.

Hardware version is C2, Firmware Version is 3.02 dated I think November 21, 2014. Did I do a factory reset after the firmware update, probably not, most routers don't need that. Anyways, if anyone has found a resolution that would be nice.

 

Logged

RYAT3

  • Level 10 Member
  • *****
  • Posts: 2254
Re: 413 - Request Entity Too Large
« Reply #1 on: February 09, 2017, 05:30:35 PM »

What are you entering?
Logged

CaseyJanke

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

Thanks for asking. Since I can't add images here, or don't know how. I put it on a web page http://mytechco.com/dir-655/

I am trying to port forward port 81 (image 1) and when I hit save I get image 2. When I click continue I go back to the router login page.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 413 - Request Entity Too Large
« Reply #3 on: February 09, 2017, 06:53:40 PM »

 Adding Screenshots In A Post

This is the FW update process:
 Link> >FW Update Process
  • Was the router working before any firmware updates?

Can you try a PC with Windows 7? I saw this once on a PC with windows 7 and the 655 that I set up at a shop I help with. However I wasn't using any PF rules. I noticed that using IE11 on Windows 7 was giving this same issue until I changed to Chrome. However updates to Chrome may have changed behaviors since then.

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 #4 on: February 09, 2017, 07:23:01 PM »

I just remoted into a computer on that network that has Windows 7 installed. Tried making the change with IE and Chrome, same problem.

As for if the router was working 'before'. The answer is yes it was working, but didn't try to add a port forward. Like many, When I get a router I plug it in and make sure it works. Before I take it to a client I always upgrade the firmware. Did I factory reset it after (or before) a firmware upgrade? No. I would hope one shouldn't have to do that. I realize there is a back up utility and such, but some configurations take a lot of time to do. If you have to factory reset a router after a or before a firmware update and start from scratch, that kind of sucks! It shouldn't do that.

However I guess my only choice at this point is to go onsite and try that. Would like to do it remotely but as I mentioned, I'm afraid if I factory reset it, the computers won't get the new ip and check in and I will lose all connection remotely.
Logged

CaseyJanke

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

If you search this error, there does seem to be issues like this (same message) in other areas of IT. It seems to me to point to a bug in the web server configuration portion of the router.

My intuition tells me that they could have implemented the port forwarding page better. The put 24 port forwarding rules on that page. Even if you enter 1 rule it is probably trying to upload the data for the whole table. If they would have just put one, then buttons to "Add Another". then maybe this problem wouldn't be happening as it wouldn't be trying to upload the whole table when many are just blank.
Logged

FurryNutz

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

I would get on site first before doing the factory reset.

The reason for doing a factory reset after a FW update is to ensure any and all configurations are fully cleared out and set up the router cleanly.
Yes the use of saved configuration files can be used, however I've seen it were there are differences between the newer FW and older saved configuration files causing problems. So even thought sometimes it defeats the purpose of saved config files, we've found that after doing the FW update and setting up the router again, saving a new config file soon after, helps avoid some issues. I've been using this method for years and has worked well each time I use it, so why I recommend to everyone here in the forums. Ensures a good installation of the FW.

This could be a issue in the FW. I'll forward this on to D-Link for review. I don't know if anything can be done since this model router is getting out of date and D-Link may not be developing on it anymore.

    This product has been discontinued.
    Free support for this product will end on 06/01/2018



 I can check my Rev C as well. I know Rev B doesn't see this issue nor did Rev A. I'll try mine this weekend.
« Last Edit: February 09, 2017, 07:53:04 PM by FurryNutz »
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.

FurryNutz

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

Please post captures of your PF rule configuration. I'll attempt to use this and reproduce on mine.
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.

RYAT3

  • Level 10 Member
  • *****
  • Posts: 2254
Re: 413 - Request Entity Too Large
« Reply #8 on: February 09, 2017, 07:41:28 PM »

Are you sure you are on 192.168.1. ?   Doesn't dlink use 192.168.0.  ? (I couldn't tell from pictures you posted). But I'm sure you understand all that so probably no luck with that.

So this camera is setup on port 81? and not 80 locally?


Logged

FurryNutz

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

He maybe using .1.# due the ISP modem maybe using .0.1.

Are you sure you are on 192.168.1. ?   Doesn't dlink use 192.168.0.  ? (I couldn't tell from pictures you posted). But I'm sure you understand all that so probably no luck with that.

So this camera is setup on port 81? and not 80 locally?
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.

FurryNutz

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

What is the Mfr and model if the ISP modem the DIR-655 is connecting too?


I realize there are other posts on this, but one ended with the person buying a new router. Does anyone have any new insights? This is crazy that I just can't add a port forward without an error.

I was going to insert the images but when I click the insert image icon all i get is . Have no idea what I'm suppose to do with that.

Basically I am trying to add a port forward and when I hit save I get "412 - Request Entity Too Large". Tried it using Chrome Edge, IE, Firefox and remotely using Opera. All yield the same. I'm not onsite now and I'm afraid if I set it to factory defaults I won't be able to access it again as the computers may not pick up the new ip address (since I'm using 192.168.1.1 sub net and it uses 192.168.0.1 by default) and I don't think there is a way to factory reset it and keep remote management enabled.

Without the port forward, the router is useless to me. So I solved one problem by moving to this router and created a new problem.

Hardware version is C2, Firmware Version is 3.02 dated I think November 21, 2014. Did I do a factory reset after the firmware update, probably not, most routers don't need that. Anyways, if anyone has found a resolution that would be nice.
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 #11 on: February 09, 2017, 07:55:20 PM »

I am using the 192.168.1 sub net because that is how the network was setup with the old router and changing that would require me to manually change the ip address of the 24 ip cameras at the site. In addition to the servers and printers, etc..

I get the FW process but it just makes it messy. What if I have 30 client sites and want to upgrade the firmware on all the routers? If I didn't have to do a factory reset I could remote in to a computer on the network and do it remotely. Having to do a factory reset means I now have to visit all 30 sites. Or even worse, what if I configured and sent one of these to my sister 2000 miles away, now I can't really upgrade the firmware remotely without bringing her into the picture to help.

The router is connecting to a Motorola SB6141 modem. Ironically, 2 days ago I took a DSR-500N onsite that I got configured at my office and was working fine, but when I took it onsite it would never get on the internet there.  I had a Cisco RV series router there that was fine, except it doesn't play nice with VOIP. So I tried the DSR-500 and couldn't connect it to the internet. Now I try a DIR-655 and it connects to the internet and their network was back up in 5 minutes. Owner wanted to go home so I figured I would finish the port forwarding stuff from home. Only to find out I can't. Arggg. I just want a silly router to work, without quirks.



Logged

CaseyJanke

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

Sorry, I forgot, yes, the camera server is 192.168.1.152 and the web server of the camera server is configured to respond to port 81. It will respond to that both locally and via the port forward (if I get it working). I used 81 so outsiders wouldn't be banging on port 80 trying to get in and wasn't sure if we were going to run their website locally or not.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 413 - Request Entity Too Large
« Reply #13 on: February 09, 2017, 08:00:22 PM »

Interesting that you couldn't get the DSR going. Haven't hear about any issues regarding that router and internet.

What wondering about ISP modem as some have built in routers and some use the .0.1 string. You can use any IP address that you wish though.

Also when your using PF rules or attempt too, you need to disable uPnP.

Please post a sample of the PF rule your trying to configure?
Can you try using Virtual Server section instead of PF?
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 #14 on: February 09, 2017, 08:01:37 PM »

Also, good thought for the future might be to use the default subnet of the router. That way you could do a hard reset and still be able to access it after. So that might be a good choice moving forward at other locations.
Logged
Pages: [1] 2 3 ... 5