Cannot access IP's from the outside

December 10, 2013 at 05:29:21
Specs: Windows 7
Please I'd appreciate your guidance on this problem. I have Win 7.

I've set up a server in my PC which worked fine from the beginning. The virtual server is properly configured in my router, pointing to 192.168.1.104. This internel IP is also reserved in the router, so it does not change.

However, during the last 30 days, the server cannot be accessed via the external IP. Also, both the server and my PC cannot be accessed from any PC in my network, either.

1. I can access server from my own PC via localhost and via the PC's internal or network IP 192.168.1.104. But the other PC's in the network cannot access my internal IP, they just can't access my PC, even to transfer the simplest of files.

2. I've checked Windows firewall and the router firewall. They're both disabled. I haven't got any other firewall set up.

As you can see, I'm practically alienated.. Any recomendations, any other checking procedures I should try ?


See More: Cannot access IPs from the outside

Report •


#1
December 10, 2013 at 07:09:40
Start by statically assigning the IP and other TCP/IP settings (Default Gateway, DNS, Subnet Mask) to the server, do not rely on a reservation. Once you've done that, exclude that IP from the DHCP scope and test from an external source. If you can't reach the server then redo the port forward on your router, deleting the old one and test.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#2
December 10, 2013 at 08:17:17
A traceroute from both the machine that can access and one that cannot would be useful.
You didn't mention port forwarding. That's vital for traversing NAT.
And what do you mean by server?
Is it an HTTP server? It may be a NetBIOS problem?
What are the IP's involved?
Does setting up the server as a DMZ help?

Report •

#3
December 10, 2013 at 09:06:42
a traceroue mas executed; my PC locates "itself" when tracert 192.168.1.104, from another PC in network 30 attempts show time ran out.

I have a LinkSys router where in "port forwarding" section it shows forwarding to port 80 IP 192.168.1.104 enabled for ALL protocols.

Server is a small HTTP UWamp server and it had been working OK for months. My internal IP is 192.168.1.104 and external is 200.75.xxx.xx. I can "see myself" via internal IP and localhost, but not via external IP.

edited by moderator: never enter your full external IP - bad idea


Report •

Related Solutions

#4
December 10, 2013 at 10:32:17
"But the other PC's in the network cannot access my internal IP, they just can't access my PC, even to transfer the simplest of files"

You either have the server firewall denying access or you have not setup peer to peer networking.

Did this work in the past?

Lets see a ipconfig /all from the server and a workstation so we can review the tcp/ip settings.

Unclear if you can access your web page when on the lan from one of the other pcs. Can you?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#5
December 10, 2013 at 11:33:39
I can access from my PC the website on server, but only using localhost and internal IP 192.168.1.104. I cannot access the website from my PC via the external IP 200.75.xxx.xx and neither the other PC's in my network can (and nobody else in internet, of course). I can access other PC's in network, but they can´t access my PC at all.

None of these things happened before...my primary concern starts with not being accesible at all within the network, especially when we need to share files. I believe this is where the blocking starts, but as I said in another post, neither the Windows firewall nor the router's are enabled.


Report •

#6
December 10, 2013 at 12:32:59
A couple of things. First, I'll repost some of wander's questions which you didn't address:

Did this work in the past?

Lets see a ipconfig /all from the server and a workstation so we can review the tcp/ip settings.

Second, I'm going to add to his last query about doing the ipconfig. Please do that on one of the workstations that can't access the web site as well as the one you're using that does so we can compare all 3.

Finally, if your setup did work correctly in the past, what was going on when it stopped. Did your ISP make changes? Did you, or someone else, make changes to your LAN? To your router?

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#7
December 10, 2013 at 13:41:21
Ok....here are my ipconfig's :

http://pppm.info/MyPC.jpg

http://pppm.info/station_pc.jpg

In several posts I mentioned everything worked fine till now.

My IP did not make changes and nobody tweaked my LAN.


Report •

#8
December 10, 2013 at 13:59:19
redo the server ipconfig /all and show us the top half not the bottom half. Thanks

You would never be able to access your web server via the lan and the external address. The request would literally have to bounce off the router wan interface back to the lan. Routers don't work like that without the ability to do a loopback. The drop the request as unroutable.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's

message edited by wanderer


Report •

#9
December 10, 2013 at 14:06:41
Click again http://pppm.info/MyPC.jpg

you'll find the upper half.


Report •

#10
December 10, 2013 at 14:31:53
The last link didn't work.

What I've noticed so far is that your "station PC" and "your PC" show different DNS IP's

If 192.168.1.1 is your router, that should also be your Default Gateway IP address and your DNS address.

All LAN clients, including your server, should have the following settings in common:
DHCP Server/DNS Server/Default Gateway = 192.168.1.1
Subnet Mask = 255.255.255.0

The ONLY TCP/IP setting that should differ in each case is the actual IP address...those have to be unique.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#11
December 10, 2013 at 15:09:35
Here's the link, it copied improperly...

http://pppm.info/MyPC.jpg

So, where do I start tweaking to make it work ? Reset the router? Disable port forwarding and ip reservation ? Connection properties ? Change TCP/IPv4 internet protocol properties I highly appreciate the effort you've shown on clearing this up...it's just that networking is not my everyday piece of pie, so please give more detail on how to start...Thanks !


Report •

#12
December 11, 2013 at 07:24:34
Do not reset anything yet!

I'm very curious why your two different client machines have different DNS addresses. Why is that do you know? As I understand it, they're both clients in the same LAN behind a SOHO router who's LAN IP is 192.168.1.1 They should both have that IP (192.168.1.1) as their DNS IP.

I also should have asked previously for the same TCP/IP information from the server as well. Could you please post that so we can compare to the client computers.

In the mean time. Change the one computer (image labeled "station_pc") to DHCP and reboot it. Once it's rebooted check the TCP/IP settings of it again and report back what they are. If the DNS entry is not 192.168.1.1 then please check your DHCP settings on the router and report back which IP you have in there.

If once you change to DHCP on that one client you do get 192.168.1.1 as the DNS, then try again to connect to your web server both by name and IP and report back what happens.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#13
December 11, 2013 at 08:37:23
All of the 10x ips listed for dns are invalid and should be removed. You need to point to a valid local or internet based dns server.

Almost appears as if you have brought up a private network on a company lan.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •


Ask Question