TP-Link AX3000 & Epson WF-2650

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

TP-Link AX3000 & Epson WF-2650

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TP-Link AX3000 & Epson WF-2650
TP-Link AX3000 & Epson WF-2650
2021-08-21 17:02:03
Model: Archer AX50  
Hardware Version: V1
Firmware Version: 1.0.4 Build 20200426 rel.69563(5553)

Just bought this router yesterday and after hours of tinkering around, I finally got it to where the DHCP Client List would see (and then let me reserve) the IPs and MACs of all the wireless clients ... save for one. I had to do this one at a time, too, and it was tedious. I had to connect with my PS3, PS4, Vizio TV, two FireSticks, my phone, and my printer and click the "Refresh" link after they connected to the router in order for them to be listed under "DHCP Client List" where I could change and reserve their IPs by their MAC addresses. The Epson Printer is the only outlier ................. but it's weird!! 

 

As the picture below shows, the Epson Printer shows up on the "Basic" and "Advanced" tabs of "Network" ...

 

 

But under "Network" --> "DHCP Server" ...... it doesn't now show at all under the DHCP Client List ... and as a result, I can't change/reserve a static IP by its MAC address. There's also a discrepancy in detected wireless clients. The pic above shows 4 ... but I have a total of 8 wireless devices on the router, and it's disappointing that my previous router (e.g. Linksys EA6350) not only had a simular web interface (and possibly same software as this AX50), but it did a better job at telling me my wireless devices apart, especially my consoles. This is the major reason why I had to connect each one one at a time -- if the DHCP Client listed the manufacturer properly (i.e. Sony, Vizio, Motorola) like my old router did, this wouldn't be that much of an issue ... 

 

Another issue with the printer and this AX50 -- under the default/shipped settings for the Default Gateway (192.168.0.1) -- it would not connect to the router in wireless mode. Not with the password. Not with WPS mode. Not with a PIN number. Furthermore, at times when it actually DID connect to the AX50 and was even visible to my Windows 10 machine and Epson's own taskbar monitoring software (and yet not listed in the DHCP Client List), it should NOT have been since the IP was listed as 192.168.1.15 (i.e. the printer's default IP)  instead of 192.168.0.15 that the AX50's DHCP Server shoudl've have given it in the first place.

 

To make things more weird, once I changed the gateway of the AX50 to 192.168.1.1, the WF-2650 would connect to the router without issue via password, WPS button or WPS pin number, and I could access the printer's web server by opening a browser to 192.168.1.15. It was there I discovered upon poking around that there's no IPv4 support in the web interface at all -- only IPv6 support ... and yet something somewhere is translating the IPv4 address to an IPv6 equivilent ... 

 

In short, I just want this printer to show up in the DHCP Client lists so I can bind its MAC to an IP ... and it never shows up! 

 

And I don't know who to point the finger at ... cheeky 

  0      
  0      
#1
Options
7 Reply
Re:TP-Link AX3000 & Epson WF-2650
2021-08-22 19:11:07

@BatRastard 

 

You should have an IPv4 IP address. Use https://whatismyipaddress.com/ to see if you have both. It is your ISP/Modem that provides the IPv4 and IPv6 addresses. Generally you get IPv4 without doing anything and need to set some parameters to get IPv6 as ISPs handle it differently.

 

Routers have different prefixes (such as 192.168.0 or 192.168.1). Some devices use one or the other prefixes. Most can be changed in the settings of the device. 

 

You should be able change the LAN IP to 192.168.1.1 in the router's advanced / network / LAN settings.  I changed mine to be 192.168.1.1 in order to be compatible with my security NVR and with my modem. I could not sign into my modem when the router was connected if I used 192.168.0.1. I had to bypass the router to sign into the modem. The NVR I could change in the NVR settings.

 

All of your devices need to use the same prefix.

  0  
  0  
#2
Options
Re:TP-Link AX3000 & Epson WF-2650
2021-08-22 21:37:01
Exactly where in your reply did you delude yourself into believing you were actually helping somebody that's been doing this since Windows 3.11/WFG ?!?!?! Not one consonant and vowel of unmitigated slop you pounded into your keyboard is relevant to me and yet people like you are THE reason why people like ME avoid tech support at all costs because there is nothing worse in the world than getting the email notification and thinking, "Hopefully that person is as knowledgably as I am and won't get my hopes up nor waste my time," and you race home from to work to find out you were better off asking the price checker at a Dollar Tree ... Re-read my post until THE fundamental question I asked sinks in, and you have a solution. Because I am now pointing the finger at YOU, and now the clock is ticking. As I stated in my original post, the is the first TP-LINK product I ever bought and YOU are the pendulum upon which swings whether or nor it's the LAST time I ever waste my time with and money with another TP-LINK and show my YouTube subscribers why ... Your call ...
  0  
  0  
#3
Options
Re:TP-Link AX3000 & Epson WF-2650
2021-08-22 23:38:13 - last edited 2021-08-23 11:55:19

@BatRastard 

point you finger anywhere you want. Note there is no TP Link by my name hence I am just an informed user trying to help others.


not my problem if you do not understand how IP address work in a router.

 

 

BTW...

 

You are a newbe compared to me as you have only been doing this since Windows 3.11.

 

I was in data processing long before there was Windows and before IBM PCs and other personal computers.

  0  
  0  
#4
Options
Re:TP-Link AX3000 & Epson WF-2650
2021-08-23 17:02:44 - last edited 2021-08-23 17:41:44

@BatRastard 

 

First I would ask that you review the Community Guidlines.  The first guideline is to be respectful to your fellow users.  Your response ArcherC8 was not that.  Further what makes it worse is that based on your response your preception was that ArcherC8 was a repretesentive of TP-Link.  While we are here to assist our customer base we do not tollerate our agents to be talk down to, just like a customer would expect our agents to be respectful to them.  So please do review this communities guidelines and follow them to continue using this service.  

 

You menitoned in your intial post that once you changed the router's subnet to 192.168.1.1  to match the subnet that the printer appeared to be on you were able to access the printer's web interface.  If that is the case that it, at least at face value, appears to be an issue in your printer.  This would further be, again on face value, confrimed since this is the only device having issues.  The Epson does appear to have a WiFi direct feature which if it is anything like HPs does create a local subnet to connect to for directly LAN printering.  This could be causing the concern, which could be IP conflict.  Another possible cause of the concern is that the printer was configured with a static IP and hence the reason it would connect.  It would attempt to negoatiate but since it was configured with a different subnet it would complete the handshake.  This could be proven by the fact that when you changed the the Router's subnet it did work.  

 

When doing the configuration it looked by your screenshot that you were working in the Tether app.  I would suggest making changes like this through the Web UI.  While each address would still need to be set one at a time you can complete all reserved addresses in one step.  Alternatively set your indidual devices with a static IP address.  You can do this by assigning any address in your subnet, but we typically recommend addresses outside of your DHCP pool to ensure you do not have any conflicts.  If you have any other questions from here please let us know but share as much as you can, including screenshots (w/o identifiying information) so that we can help to our fullest extent. 

  0  
  0  
#5
Options
Re:TP-Link AX3000 & Epson WF-2650
2021-08-23 18:47:55

@Carl Thanks for the response ...

 

First off, let me clarify that with the gateway at its default (192.168.0.1), the printer would not connect at all when I forced it to, but after rebooting the router, the printer's display would show it was connected, that it's IP was 192.168.1.1, the taskbar monitor would detect and show ink levels, and print a test page. This is behavior it shouldn't be doing since it's a subnet conflict ... 

 

That's when I changed the gateway on the router to 192.168.1.1 and after the router reboot, I reconfigured the printer just to gauge whether it would time out and instead connected within 8 seconds ... 

 

I'm writing this off as Epson's issue as it's apparent that they hard coded the IP in their latest firmware as previous firmware and software for their Workforce line has always been wonky ... 

 

The screenshot is actually from the Web Interface but cropped as to not reveal anything else regarding my setup, and I'm not a fan on blacking things out. It's from the screen right after logging in. It shows the printer, and clicking it shows the IP address as 192.168.1.15, but in the DHCP Client list, it doesn't show up, thus I couldn't reserve the IP by MAC address. It's the only wireless device on my network displaying this behavior so yeah ... It's all on Epson! 

 

I did make the router lock up at one point. I'll recreate the steps that did it and see if it was just a one off or not and get back with you. 

  0  
  0  
#6
Options
Re:TP-Link AX3000 & Epson WF-2650
2021-08-23 19:08:19

@BatRastard 

 

Sounds good.  Please do let us know.  We are here to help and will address any issues that are happing with our products.  If you want a direct response from TP-Link just tag @Carl  or @Ryan  and we will be happy to assit. 

 

For the Device List it looked like how the app displays devices so I wanted to make sure.  Also one reason the device name may not displaying is that it was not transfered in the handshake with the router. so if you continue to have issues with the name broadcasting in the router's device list please let me know that so we can work with the engineering team to see if it is a concern in the router that can be resolved 

 

  0  
  0  
#7
Options
Re:TP-Link AX3000 & Epson WF-2650
2021-08-23 22:05:15
It was a one off ... I recreated the steps and the router never froze again. :) I have a Netgear WNDR3800 in the bedroom running Gargoyle firmware, and when I saw it listed in the Basic section of the AX3000, there's also a little icon in the upper right. I clicked it, noticed that I could rename it, so I renamed it "Gargoyle Router", and that's what triggered the freeze the first time. I had to power cycle the AX3000. Well, I just tried to rename it back to "Gargoyle" and "Gargoyle Router" and the AX3000 took it like champ ... I'm also an idiot for not noticing "Advanced Mode" --> "Security" --> "Access Control" & "IP and MAC Binding" and seeing the option to blacklist/whitelist my devices ... including the Epson printer! It shows up there with no issue. Bah, I don't need to go that far. The printer connects. It prints from both my PC and my Android phone. I can ping it. I can access its web interface. Good enough for me! The AX3000 runs a bit warm though ... But so does the Netgear CM500 right next to it ... They're about the same temperature ...
  0  
  0  
#8
Options