View previous topic :: View next topic |
Author |
Message |
Guest
|
Posted: Fri Nov 08, 2002 7:04 pm Post subject: Connection problem: I am totally baffled! |
|
|
The problem: I can access AWS by going to "localhost" or 127.0.0.1. People from the outside can access my AWS as well. However, I can't access my AWS from either PC on my local network, if I try accessing it using my WAN IP or domain name.
In other words, for ME and me alone, http://127.0.0.1:port/ works, but http://IP:port/ does not work.
My ISP blocks incoming port 80, so I am using port 8009. I have a router, and of course I am forwarding port 8009 to the PC running AWS. I have my software firewall correctly configured as well. The proof of this is that other people can access my AWS.
The URL is http://someurl.com:8009/ , and I expect that it will work for you, so long as I have it running at the time.
I am totally baffled and aggravated by this. |
|
Back to top |
|
|
Scott -
Joined: 08 Nov 2002 Posts: 16
|
Posted: Fri Nov 08, 2002 7:18 pm Post subject: |
|
|
Oops, stupid me, I neglected to login before posting before.
Just to add... I have tried running the AWS-based PC in DMZ, and I've tried disabling the software firewall. I've looked in the router logs, and see absolutely nothing. I've checked the AWS "access.log", and it my connection isn't even getting through to it. |
|
Back to top |
|
|
aprelium -
Joined: 22 Mar 2002 Posts: 6800
|
Posted: Sat Nov 09, 2002 1:42 am Post subject: Re: Connection problem: I am totally baffled! |
|
|
Anonymous wrote: | The problem: I can access AWS by going to "localhost" or 127.0.0.1. People from the outside can access my AWS as well. However, I can't access my AWS from either PC on my local network, if I try accessing it using my WAN IP or domain name.
In other words, for ME and me alone, http://127.0.0.1:port/ works, but http://IP:port/ does not work.
My ISP blocks incoming port 80, so I am using port 8009. I have a router, and of course I am forwarding port 8009 to the PC running AWS. I have my software firewall correctly configured as well. The proof of this is that other people can access my AWS.
|
You must have an IP which is valid only inside your LAN and this is the IP you must use for local access. You can get that IP by executing on the command line ipconfig (on WinNT/2000/XP) or winipcfg (on Win95/98/Me).
Using one of these command gives you the IP assigned to your network card on your LAN. _________________ Support Team
Aprelium - http://www.aprelium.com
Last edited by aprelium on Tue Feb 18, 2003 8:57 pm; edited 1 time in total |
|
Back to top |
|
|
Scott -
Joined: 08 Nov 2002 Posts: 16
|
Posted: Sat Nov 09, 2002 3:03 am Post subject: |
|
|
Thanks, but I knew that. I know all about "WAN IP" vs. "LAN IP". The problem was I could only access my server using my LAN IP, while others could access it via the WAN IP. However, it seems to me I should be able to use either one!
Never mind, I give up on this. Thanks for the reply, though. |
|
Back to top |
|
|
aprelium -
Joined: 22 Mar 2002 Posts: 6800
|
Posted: Sat Nov 09, 2002 4:50 am Post subject: |
|
|
Scott wrote: | Thanks, but I knew that. I know all about "WAN IP" vs. "LAN IP". The problem was I could only access my server using my LAN IP, while others could access it via the WAN IP. However, it seems to me I should be able to use either one!
Never mind, I give up on this. Thanks for the reply, though. |
Just a small tip. On your computer, locate the hosts file:
* On Windows 95/98/Me c:\windows\hosts
* On Windows NT/2000/XP Pro c:\winnt\system32\drivers\etc\hosts
* On Windows XP Home c:\windows\system32\drivers\etc\hosts
If not available create it (with no extension), just hosts and not hosts.txt .
Edit it using Notepad and add the following line
127.0.0.1 my.dnsalias.net
or if you LAN IP is 192.68.0.1:
192.68.0.1 my.dnsalias.net
Save the file and close Notepad.
Than way, when you ask for my.dnsalias.net on your computer, it will point to the correct LAN IP without asking an external DNS server which will return your WAN IP.
Nice ??? :D _________________ Support Team
Aprelium - http://www.aprelium.com |
|
Back to top |
|
|
Scott -
Joined: 08 Nov 2002 Posts: 16
|
Posted: Sat Nov 09, 2002 5:00 am Post subject: |
|
|
Thanks. I knew about Hosts, but hadn't thought about that workaround. It's a good tip, and I'll use it.
But I still should be able to access what "my.dnsalias.net" resolves to. And it drives me nuts not knowing why I can't! Oh well...
Thanks again, though; I really appreciate the input! |
|
Back to top |
|
|
aprelium -
Joined: 22 Mar 2002 Posts: 6800
|
Posted: Sat Nov 09, 2002 5:24 am Post subject: |
|
|
Scott wrote: | Thanks. I knew about Hosts, but hadn't thought about that workaround. It's a good tip, and I'll use it.
But I still should be able to access what "my.dnsalias.net" resolves to. And it drives me nuts not knowing why I can't! Oh well...
Thanks again, though; I really appreciate the input! |
May be
Code: |
tracert my.dnsalias.net
|
can give more information about the "wrong" way TCP/IP packets take ??? _________________ Support Team
Aprelium - http://www.aprelium.com |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|