Trying to configure a Print Server that is in a remote location

[Mr Davo]

Hi Everyone,

I am attempting to configure a TP-Link TL-PS110P Print Server from a remote location.

From my location I am accessing a laptop which is connected to the same physical network as the Print Server. However the laptop has an I.P. address of 192.168.170.10, and it is connected directly into a router with the I.P. address of 192.168.170.254, whereas the Print Server has a default I.P. address of 192.168.0.10.

Within the laptop I have set a static route to the Print Servers I.P. address, below is a screen capture of the laptops route table.

As can be seen above (in yellow highlight) there is now a route from the laptop to the Print Server. However I am unable to ping the Print Server, and entering the Print Server's address into a browser results in no configuration page being loaded.

All this being said when I use a Network detection program I can clearly see that the Print Server can be reached on the network, as shown below.

How can I go about loading the Print Servers configuration page through a web browser? I have tried http://192.168.0.10, and https://192.168.0.10. Furthermore the same network has an identical TP-Link Print Server connected, and I can reach it's configuration page (due to it being on the I.P. address 192.168.170.229), and I can see that by default the Print Server does not require an explicit Port number to be specified.

I am quite stuck here, any suggestions will be greatly appreciated.

Kind Regards,

Davo

 

[chev65]

It seems like the persistent route would need to start with the IP of the printer which ends with .10... rather than .0 although I'm a bit confused on the requirements here.

So assuming you want a persistent route...,

route -p add 192.168.0.10 mask 255.255.255.0 192.168.172.254 metric 1

To remove or to delete the old entry, type this: “route -p delete 192.168.0.0" or which ever IP it starts with" assuming it's persistent.

Another trick to check and edit your persistent routes is through the system registry.
In your regeditor follow this path:
HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->
->Services->Tcpip->Parameters->PersistentRoutes

 

[Mr Davo]

Hi chev65,

I started with the route add command that you suggested, and essentially only added the one route to 192.168.0.10, however after this I decided to add a route to all 192.168.0.xxx addresses by creating a static route to 192.168.0.0 with the mask of 255.255.255.255. However I am not particularly strong with adding static routes so please let me know if you think that the command I issued did not achieve what I had intended.

Kind Regards,

Davo

 

[chev65]

Hi chev65,

I started with the route add command that you suggested, and essentially only added the one route to 192.168.0.10, however after this I decided to add a route to all 192.168.0.xxx addresses by creating a static route to 192.168.0.0 with the mask of 255.255.255.255. However I am not particularly strong with adding static routes so please let me know if you think that the command I issued did not achieve what I had intended.

Kind Regards,

Davo

As I read this the static route needs to start with the IP of the device to be routed and needs to route to the gateway device or router but I haven't messed with static routes enough to really know for certain the exact command required in this case.

I was just showing the route command for what I was seeing in your first post but this isn't something I do everyday either and it would be interesting to see which commands are working for this.

You can also set up static routes using the router's firmware settings which might work better in some cases.

Perhaps some trial and error will be needed, while deleting the route's that don't work using the command prompt or/and checking the registry to make sure the route is removed before you issue the new command.