Networks

Ask something
Discussion Locked

Remote access port forwarding problem

0 helpful
5 replies

by malecken

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Linksys wireless router\switch which is performing NAT for our web access. This router also supports Port Forwarding.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. I have set up the router to forward a particular port to a local desktop with class C private address. Port is open on local desktop(Win2K box). After entering browser info.(xx.xxx.xxx.xxx/xxxx), I get login dialog for router. Even CORRECT router admin. password doesn't work(it works locally), but I don't think I want this dialog anyway. Win2K Incoming Connections is set to let others come in via VPN or PPTP. I have spent 2 hours on phone w\Linksys trying various things, and scoured web sites looking for help. Good tips, but nothing works. HELP!!!!!!!!!

5 replies

by sgt_shultz

what modem router? what remote control software? no other firewalls anywhere? are you sure your are specifying the ipaddress/port correctly?

by cg it

I'll answer again. Regardless of what you want, you can not have NAT enabled on the router and use port fowarding. It will not work as port fowarding fowards requests to a specific IP address [you'll see that in the port fowarding properties page. It will ask what protocol eg TCP or UDP and what IP address on the LAN then enable that fowarder.] PPTP inbound TCP requests come in on port 1723. Even with PPTP pass through enabled unless a fowarder is provided, it doesn't know where to go. Your WANIP address is provided by your ISP and is how Internet users find you. In creating a connection from the internet, uses have to use your public ISP provided IP address eg 10.10.1.1 [with no port specified the default if port 80 which is HTTP] Users can specify a port eg 10.10.1.1:2300 or use a FQDN or CName or Host name. Unless you've specified that the router fowards that inbound port 2300 request to specific LAN computer, specified in the port fowarding properties page by a specific IP address, the request gets discarded.

That seems to be happening to you.

Disable Router NAT, create an IP address for your LAN computer with the router as the gateway and DNS as your ISP DNS. In the router's port fowarding properties specify that particular computer [by IP address you've just created]to receive inbound port traffic. Inbound requests via that particular port will then be fowarded to that particular computer.

You can not connect to a LAN computer via the internet by using the routers IP address. That will only bring up the routers Administration page. You can only connect to LAN computers via the internet by using your Public IP address [eg the one assigned to you by your ISP].

by cg it

Ha! didnt read my mail before answering. Ok, you still don't have remote access to your W2K machine even on DMZ. Check your Routing and Remote access services in administration tools on your W2K machine. Default is disabled. You have to enable Routing and Remote access service on the W2K machine to get remote access and have that remote access interact with the desktop. Also security settings for a particular user has to allow remote access to the machine. Specify a user in the local machine security properties, "access this computer from the network" properties to allow particular users or computers to access the computer.

A remote user has to create a new network connection in the Network & Dial Network connection properties in the control panel. Here they specify their user name, password, domain name [if any, or workgroup] how eg the IP address and port # and what type of authenitcation they will use.

To explain PPTP this type of remote access protocol use a specific port specified by RFC. PPTP uses port 1723. For a remote user to access via PPTP, port 1723 has to be open to service PPTP inbound requests and the router has to foward that inbound request to the appropriate computer that allows inbound PPTP traffic.
Another way to remotely connect is through terminal services [which is how most small networks operate that don't have a W2K server with Routing and Remote access services.]

Still another way is to use a third party program like PC Anywhere [which is somewhat expensive]. There are other remote access 3rd party programs available but off hand, none come to mind.

by cg it

Windows XP simplified this entire process with Remote assistance [which is a security hole but still really makes the whole remote access process a lot easier].

This discussion is closed to new replies.