Resolving local PC names on non-windows devices
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Resolving local PC names on non-windows devices
Region : UnitedKingdom
Model : TL-WDR4300
Hardware Version : V1
Firmware Version : 3.13.23 Build 120820
ISP :
Region : UnitedKingdom
Model : TL-WDR3600
Hardware Version : V1
Firmware Version : 3.13.23 Build 120820
ISP : BT Infinity
I am running a Windows Home Server machine called "mserver" that has an IP address supplied via DHCP.
There is also a local webserver running on port 8089 that I use to access media from several devices (Android Phone, Blackberry Playbook & HP Touchpad...i.e. not Microsoft).
When I had the BT Homehub3 in use I could access the webserver via http://mserver:8089 and it would be loaded on all devices.
With the WDR3600 used in place of the Homehub3 it cannot resolve mserver into a local IP address on a non windows device. I can access it via http://192.168.0.xxx:8089 so the route is there.
Does the WDR3600 have any local DNS resolution? I repeat the BT HomeHub3 CAN do this, so why can't the TP-LINK?
Cheers
Mike
P.S. I have tried :-
Disabling hardware NAT
Turning off UPNP & Port Forwarding
Restoring to factory default
Disabling all ALG's in security
Model : TL-WDR4300
Hardware Version : V1
Firmware Version : 3.13.23 Build 120820
ISP :
Region : UnitedKingdom
Model : TL-WDR3600
Hardware Version : V1
Firmware Version : 3.13.23 Build 120820
ISP : BT Infinity
I am running a Windows Home Server machine called "mserver" that has an IP address supplied via DHCP.
There is also a local webserver running on port 8089 that I use to access media from several devices (Android Phone, Blackberry Playbook & HP Touchpad...i.e. not Microsoft).
When I had the BT Homehub3 in use I could access the webserver via http://mserver:8089 and it would be loaded on all devices.
With the WDR3600 used in place of the Homehub3 it cannot resolve mserver into a local IP address on a non windows device. I can access it via http://192.168.0.xxx:8089 so the route is there.
Does the WDR3600 have any local DNS resolution? I repeat the BT HomeHub3 CAN do this, so why can't the TP-LINK?
Cheers
Mike
P.S. I have tried :-
Disabling hardware NAT
Turning off UPNP & Port Forwarding
Restoring to factory default
Disabling all ALG's in security
