PLEASE HELP!! Can connect within network, but not anywhere else

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am hooked up at work with 4 other computers and I can get remote desktop
from all the others, but when I try from home or any other computer I can't.
I always get the message saying the remote isn't turned on at the host, there
are too many users or there is a network problem. How can i fix this? I
believe it has something to do with the router, but not sure. Please help!!!!!
 
You need to forward/open TCP Port 3389 through any firewall/router to the
private static LAN IP of the PC you want to remotely access/control. See
this page for help...

http://theillustratednetwork.mvps.o...pSetupandTroubleshooting.html#Port_forwarding

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Thank you so much for the response...BUT how do I do that? I have a linksys
router for the 4 computers and I can't get into the router to change it. I'm
confused as to how to find my current router ip to get into it to change the
port. And i'm not sure even if i get in that i'll know what i'm doing. Any
help? I'm pretty familiar with the computer, but this stuff is a bit over my
head so i'm doing my best. Thanks in advance.
 
What Linksys router? That information would be a big help for someone to
help you...:-)

Ignore references to UDP Port 3389 since it is not used...

http://www.portforward.com/english/applications/port_forwarding/RemoteDesktop/RemoteDesktopindex.htm

In general to get into most if not all Linksys routers you use the
http://192.168.1.1 address in Internet Explorer from one of your local PCs
with a blank/empty/null user Id and a password of 'admin' without the
quotes.

See this page for help addressing from a remote location...

http://theillustratednetwork.mvps.o...ktopSetupandTroubleshooting.html#Call_Schemes

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Okay...I got into the router and made the TCP 3389 open to the static IP of
my remote computer. But then I tried it again and it didn't work. I still can
connect through the other 4 computers in the network, but not from outside
it. Do i have to type in a username, password and domain to make it work?
 
Yes, you need a username and password which is local to the PC your trying
to remotely access/control. Also make sure when you test you are *NOT*
calling from another local PC on the same LAN but using the public IP of the
router. That is not a valid test.

http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html

Also from the PC you want to remotely access/connect to you can run this
test from the http://www.canyouseeme.org site to see if you have port
forwarding setup correctly...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Okay...here's what's up. I have opened 3389 using the link from the last link
you gave me and nothing. I changed the WAN blocking as the website said.
Still nothing. On portforwarding.com on the directions it has 192.168.1.xxx,
but when i open up my linksys router i am only given 192.168.100.xxx (100
instead of 1). Could that be it? Also, when I try to login from a public PC
should I use the name of my computer or the IP? And if it's the IP do I put
192.168.100.155 which is the static IP on my remote computer? Or do i put
something like 192.168.100.155:3389? also do i have to put in a DOMAIN? I
can't find one on the router signin? I also changed my TCP port from 80 to
another number. Should i switch it back or does it matter?
 
Okay, so i did everything you said to do as well as portforward.com. I went
through and switched something for the WAN blocking as noted by
portforwarding.com. The only thing was they kept telling me to forward the
3389 port an IP address of 192.168.1.xxx, but when i login to my router i'm
only given 192.168.100.xxx options (100 instead of 1). could that be it? when
i login from an outside PC (which I'm testing from) do i use my computer name
or my static IP address on the remote computer? Do i HAVE to put in a DOMAIN?
When i input an IP (if I have to) do I just put 192.168.100.xxx or do i put
something like 192.168.100.xxx:3389?

I also switched my TCP port from 80 to another number? Should i switch it
back and does that matter?
 
If the local LAN is configured for 192.168.100.X addresses then you would
forward to the appropriate address the PC is assigned. Go to "Start -> Run"
and type cmd in the command line. At the prompt use the command "ipconfig"
to get the IP of the PC you want to connect to. Use that IP in the port
forwarding configuration on the router.

As far as the IP you use to call from a remote location you can go to
http://www.whatismyip.com from a PC on your local LAN and get the IP your
ISP has assigned. Use that IP to call from a remote location. Keep in mind
that most residential users get dynamic IPs from their ISP. If that is the
case keep in mind the IP may change over time. One way to get around that is
to use a dynamic naming service like No-IP.com that maps a fully qualified
domain name to your IP. You can then call home using the fully qualified
domain name.

http://theillustratednetwork.mvps.o...ktopSetupandTroubleshooting.html#Call_Schemes

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
Al-

I just want to say thank you for all your help you've given me in the past 2
days. I really appreciate it.

Now, I've done everything you've said for me to do and I have not been able
to get it to work. I used the IP my remote computer uses (192.168.100.xxx
when I use ipconfig) and then I tried to sign on using the IP that my ISP
provided and still...no connection. I did speak with tech support at my
office and he said we actually have another 'router' that our connection goes
through. I work in an office where there is one big company, but then
individual businesses running under that one big one so our connection runs
through two routers I guess. So I'm thinking that I might have to get the
tech guy to open 3389 and forward that to my company router IP which is
67.39.95.107 with TSP. That way it will go thorugh the 3389 port to my
company router where it will be forwarded to my 192.168.100.xxx which MY
remote computer is assigned to. Do you think that will work?

Do i have to put anything in DOMAIN section when i sign on for a remote
connection?

I changed my TCP port from 80 to another number...does that make a
difference? Should I switch it back?
 
Yes, the other router, ie. the one that actually interfaces to the public IP
needs TCP Port 3389 forwarded/opened to the IP of your router. Is the
69.39.95.107 IP the address assigned by the other router or the ISP?

Your reference to TCP Port 80 is also confusing. Are you trying to use the
web based Remote Desktop method? If so then that certainly complicates the
connection. In that case you would need both TCP Port 80 (IIS) *AND* TCP
Port 3389 (RDP) forwarded through both routers. Personally I see little gain
from using the web based method in most cases.

Unless your in a domain environment, ie. using a Windows 2003/2000 Server,
you don't need the domain entry.

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
It's actually the assigned IP for my router...does that make a difference? I
will contact the tech guy and have him open 3389 and forward to 67.39.95.107
which is the assigned IP from my router. If that doesn't work...I'll be back!
Thanks again.

I really didn't know what i was doing when I switched my TCP port from
80...I guess I was just grabbing at straws trying to get anything to work.
I'll switch it back and make it normal. I wasn't trying to do anything
web-based, but I guess I was looking at an article on web-based access.

Thanks again.
 
Yes have him forward TCP Port 3389 through his router to the 67.X.X.X
address and you should be good to go presuming you have forwarding
configured correct in your router...

Good luck...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
I just got a message from my tech guy and he has to go on vacation for few
days and he said he would look at it when he gets back ;-/ Arg!! But what are
you going to do. He said he knows exactly what you mean about opening ports,
but considering it's on a much bigger scale and on a much bigger router he'll
have to do some research to open and forward the port. He said he's done it
on his home network, but not on a large scale one. I'll keep you posted.

Thanks again!
 
Back
Top