7 replies
by cg it
what appears to be happening is remote access for the router management console ["I want remote users to access a local desktop(which is using a remote access app. to be a host) via web browser, by entering NAT router's public IP address and a port number"].
The admin password not working could be a filter. Check the filters property page and see what port they have specified [usually port 8080] and whether or not Remote Management is enabled. BUT I don't think your intent is to allow remote users to be able to manage your router.
Question: Do you have the router setup as a DHCP server suppling clients with IP addresses? If so, that's 90% your problem. For port fowarding to work, LAN client connecting to the router have to have a static IP address.
Though the router will "pass through" PPTP most of the time you have to configure the TCP PPTP port 1723 and I believe GRE UDP port 47 to get what you want to work and then it's to a specific computer on the LAN [re static IP address specified in the port fowarding properties page of the linksys router].
A workaround to the problem of fowarding PPTP traffic is to put whatever computer you want remote users to access on the DMZ.
by cg it
by malecken
by malecken
by malecken
by malecken
by lenz.rudiger
Yes you need to forward those ports to your internal "Hosts".
Be CAREFULL this is very unsecure!! You open your network, virtually without any protection.
Some information for PPTP:
PPTP consists of two connections running across very different protocols. The PPTP control connection runs across TCP via port 1723 and the data runs on top of IP GRE (type 47 or UDP). Most router & firewalls don't allow IP Type configuration, therefore UDP is used. GRE-UDP packets are UDP packets with destination port 47.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending