After bridging modem i can no longer download directory

[Nydilius]

Hello all, I'm hoping someone can help a "green" user with this issue.

I have 2 pc's behind my router, one for server one for use. Previously i had a filezilla server setup that worked great for almost a year. Then i ran into an issue with my router/modem and port forwarding (stupid app controlled garbage), so i bridged it to a proper router. It worked wonderfully and cleared up all my issues with other software, but my FTP server just wont work now.

I have ports forwarded (21-27, 990, and passive 50000-51000) copied from my old router/modem, and made no changes to my current server settings. I can log into the server but it times out when trying to download directory. I have tried every troubleshooter i could find, updated the server, and tried both setting and leaving blank the "Use the following host" field in the passive mode tab.

This issue is driving me nuts and any help would be much appreciated. (im not sure what the protocol is for posting error logs and such so i am sticking to a description for now to avoid fopah's )

[botg]

im not sure what the protocol is for posting error logs

The more the merrier.

[Nydilius]

Sounds good.

This is the message i get on the client when trying to access the server from my workplace.

client.JPG (35.95 KiB) Viewed 367 times

This is the message i get on the server at home.

server.JPG (93.62 KiB) Viewed 367 times

I have double checked firewalls on the server, all the rules for allowing the .exe through and ports are open are there. incoming and outgoing. Even tried disabling firewalls completely and setting the server up as a DMZ on the router for a short while to see if that would help. No luck.

[botg]

The log has been censored, so impossible to see what is going on. Is the IP address you are connecting to the same as you see in the PASV response?

[Nydilius]

correct. all instances of the IP on both client and server are referring to my external IP, with the addition of a ",196,197" at the end. these last two numbers seem to change with every attempt.

[botg]

Last two numbers denote the passive mode port. 196*256+197 = 50373, which is inside the aforementioned range.

Speaking of ranges, make sure you don't have one of those stupid routers that, if given a range, map all ports in the range onto the first one in the range. 50000 should go to 50000, 50001 to 50001 and so on,

[Nydilius]

I attempted to individually forward each port from 50200 through 50220 to see if this was the case. same results.

[botg]

Does it work if you bypass the second router and connect the server directly to the bridged device?

[Nydilius]

I tried it just to be sure but no luck. The port forwarding on the original router/modem was always touchy, its why i bridged it to begin with, so while it was working before bridging the act of powering it on and off and changing settings seems to have borked it.

However, i do think trying it may have helped narrow down the problem to the new router. The new router is a DLink AX1500 R15 router. The act of powering it down then up again when disconnecting it seems to have "scrambled" the port forwarding settings. It seems on startup it chose a random selection of ports on the forwarding list to allow through and ignored others. Before this test i could use port 27 to login, but the passive ports were a no go, along with a port range i attempted to setup for a game server. After rebooting its not forwarding port 27 anymore (cant connect to server at all), but the game server is open.

This was the same issue i had with the original router/modem (that and it required that godawful bluecurve app to do anything with). When i purchased the router i didnt do alot of research, i figure its like printer, such mainstream tech how could it go wrong. Maybe its a lemon? or am i overthinking and should keep my eyes on software settings?

(swear, this issue is causing my hair to fall out in frustration, ill be sporting a picard soon! )

[botg]

The new router is a DLink AX1500 R15 router. The act of powering it down then up again when disconnecting it seems to have "scrambled" the port forwarding settings.

That's a failure mode of cheap (to manufacture) routers I haven't seen yet. They keep surprising me.

(swear, this issue is causing my hair to fall out in frustration, ill be sporting a picard soon! )

To baldly go where where no man has gone before