ive been having some ip adress problems... I got my apache 2.2 based hardrive acting as a server up, working with my privet IP and throughout my network. I then went to whatismyip.com and checkip.dyndns.org and saw that my public ip was 64.x.x.x . i tryed putting that in my browser, with and without " http:// " and it did not foward to my site. I then called my ISP and they said that they did provide me with a public IP and it was 172.x.x.x . i tryed that and it didnt work either, it also didnt work on tech support's comps. i set all the permissions right to accept all computers in apache and my share drive prefs. my ISP's tech support was stumpped, the ip they gave me was pinging 100%. does anybody have any ideas of what might be up? also, sry for all of the typos :)

Have you forwarded port 80 from your router to the computer hosting the server. Unless you do, the server never gets to see any external HTTP requests. Both dyndns and your ISP might be right if you have a dynamic IP address. Is it dynamic or static? Stuart

heres whats going on ______________ tech guy Are you forwarding port 80 from your firewall to your web server? me i opened all ports from my firewall and ended up just turning it off for the web drive edit i specifically listed port 80 as an exeption and allowed apache and other applications to run without interference im not quite sure what you mean by forwarding it tech guy I mean no offense, but it might be a good idea to study up a bit on network concepts, especially NAT and PAT. These will really help you understand what I mean. On the topic of troubleshooting try a traceroute to a root DNS server. I don't know what OS you run, so in Windows it's like this: Code: tracert 4.2.2.2...and in Linux, BSD, or MacOS X it's like this: Code: traceroute 4.2.2.2... then post the results. That will let us know what's between you and a core part of the internet. me wow, thanks for the that trace command... anyway here are the results 192.168.1.1 172.18.128.1 vlan3.core02.rose.net (172.17.1.21) f1-1.igr01.rose.net (64.39.128.1) 65.198.220.85 67.98.191.77 p2-3.c0.atln.broadwing.net another broadwing ip another broadwing ip 216.140.8.5 ge-6-10.car3.washington1.level13.net yeah, im kindof new to networking. edit but, i think that maby, when i go to the 172 .17..... ip, it cant defer between the 5 computers connected. anyway i could get it to go to my server instead of get confused with the other connected comps? tech guy Thanks for the trace, that helps. Based on the differences between your first public address (in the 172.18.128.x network) and the address you're actually coming into the forums with (64.39.x.x network), it appears that something upstream of you is NAT'ing your address. This is 64.39.137.137, whatever that is. If you're using a proxy server, that could be it. Otherwise, if that's a router, it appears to be between you and the rest of the Internet, and it appears to be NAT'ing your traffic. So, we (the rest of the internet) can't actually reach your 172.18.128.x network at all, we only get as far as your ISP. Here's a traceroute from my network to your public IP: Code: $ traceroute 64.39.137.137 traceroute to 64.39.137.137 (64.39.137.137), 30 hops max, 40 byte packets 1 Michael.SatelliteOfLove (192.168.25.1) 0.403 ms 0.237 ms 0.170 ms 2 netblock-68-183-49-1.dslextreme.com (68.183.49.1) 21.789 ms 12.270 ms 11.899 ms 3 LAX1.CR1.Gig6-0-10.dslextreme.com (66.51.203.17) 36.328 ms 15.521 ms 11.776 ms 4 netblock-66-51-198-166.dslextreme.com (66.51.198.166) 12.264 ms 12.245 ms 13.072 ms 5 p1-0.core02.lax01.atlas.cogentco.com (154.54.2.237) 144.302 ms 171.479 ms 65.854 ms 6 p12-0.core01.lax01.atlas.cogentco.com (66.28.4.241) 67.030 ms 30.212 ms 34.958 ms 7 t3-1.mpd01.lax01.atlas.cogentco.com (154.54.2.102) 15.209 ms 168.678 ms 203.347 ms 8 t2-2.mpd01.iah01.atlas.cogentco.com (154.54.3.37) 96.905 ms 208.939 ms 234.351 ms 9 g11-0-0.core01.iah01.atlas.cogentco.com (154.54.5.197) 50.642 ms 45.711 ms 45.225 ms 10 p3-0.core01.atl01.atlas.cogentco.com (154.54.5.90) 77.678 ms 86.937 ms 87.255 ms 11 v3802.na01.b002053-0.atl01.atlas.cogentco.com (38.20.34.62) 99.460 ms 82.985 ms 98.611 ms 12 Georgia_Public_Web.demarc.cogentco.com (38.112.26.46) 82.661 ms 111.610 ms 109.921 ms 13 66.110.192.221 (66.110.192.221) 235.589 ms 90.323 ms 96.877 ms 14 66.110.192.18 (66.110.192.18) 94.363 ms 116.388 ms 87.474 ms 15 65.198.220.86 (65.198.220.86) 84.941 ms 107.586 ms 100.801 ms ...and that's as far as it gets, a router at your ISP is blocking my traceroutes from going any deeper. me yeah, i had a guess my linksys had something to do with it. do you know any configurations i could make that would change that. and also, if i got a split so i could wire my server strait to the modem, would that make it work? tech guy Whoops, was I thinking? Your traffic is all private until it gets to f1-1.igr01.rose.net (64.39.128.1), the 172.18.x.x network is an RFC 1918 reserved network. Off Topic: For some reason I read "172.18.x.x" as "172.8.x.x" in my mind... Are you saying that you have two routers? me no. 1 wifi router 1 modem tech guy Are you sure your 'modem' is not a 'modem/router'? Does it have any firewall features? An interface you can login to? Can you tell us the make & model? me router- linksys wireless G broadbandrouter with speedbooster model ezx555w modem- terayon tj715 edit: newly bought 5 port switch- linksys 10/100 5-port workgroup switch me ok, so, going on the idea that my router was changing my pub ip, i went out and bought a 5-port switch so i could plug my server and my router into the modem at the same time without the ip changing. I then did a tracert and found that yes, it did not change my pub ip but, it bypassed my privet. Now i cant accsess my index from anycomp and my apache wont start up. Code: ( error says: only one usage of each socket address <protocol/network address/port> is normally permitted. : make_sock: could not bind to address 0.0.0.0:80 no listenting sockets available, shutting down unable to open logs apache config files: Code: # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If your host doesn't have a registered DNS name, enter its IP address here. # ServerName 172.18.128.1:80 # # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # DocumentRoot "D:/" ------------- # ThreadsPerChild: constant number of worker threads in the server process # MaxRequestsPerChild: maximum number of requests a server process serves ThreadsPerChild 250 MaxRequestsPerChild 0 # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # Do not add a slash at the end of the directory path. If you point # ServerRoot at a non-local disk, be sure to point the LockFile directive # at a local disk. If you wish to share the same ServerRoot for multiple # httpd daemons, you will need to change at least LockFile and PidFile. # ServerRoot "D:" # # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, instead of the default. See also the <VirtualHost> # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses (0.0.0.0) # #Listen 12.34.56.78:80 Listen 80 and, my tracert says: (c local drive) Code: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Administrator>tracert 4.2.2.2 Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2] over a maximum of 30 hops: 1 10 ms 10 ms 10 ms 172.18.128.1 2 10 ms 11 ms 9 ms vlan3.core02.rose.net [172.17.1.21] 3 13 ms 10 ms 10 ms f1-1.igr01.rose.net [64.39.128.1] 4 20 ms 23 ms 13 ms 65.198.220.85 5 24 ms 18 ms 28 ms 67.98.191.77 6 19 ms 18 ms 18 ms p2-3.c0.atln.broadwing.net [216.140.12.1] 7 30 ms 39 ms 30 ms p3-0.c0.wash.broadwing.net [216.140.8.109] 8 30 ms 28 ms 32 ms p0-2-0.a1.wash.broadwing.net [216.140.8.90] 9 30 ms 48 ms 30 ms so-2-2-0.a1.wash.broadwing.net [216.140.8.162] 10 32 ms 33 ms 33 ms ge-6-10.car3.Washington1.Level3.net [4.68.127.25 3] 11 32 ms 32 ms 33 ms ge-5-0-51.hsa1.Washington2.Level3.net [4.68.121. 13] 12 31 ms 34 ms 30 ms vnsc-bak.sys.gtei.net [4.2.2.2] Trace complete. C:\Documents and Settings\Administrator>as you can see, it skipped my local and my comp wont read the local thanks for any ideas

172.18.xxx.xxx is a Class B private IP address not a public one. The private address is usually the one provided by your router via DHCP. The public IP address is provided by your ISP. NAT (Network Address Translation) translates betwen the two. Home routers uaually use a Class A private Ip address in the range 192.168.xxx.xxx. This has been changed in the router configuration. The server name should be a public IP address, not a private one. Ideally the server namme should be a URL but an IP address will do. You need to do two things. Read up on NAT, DHCP and port forwarding, public and private IP addresses. Until you do know how you will never be able to run a web server through a router. You also need to read the routers manual. That will tell you how to forward ports to the web server. I would also read up on web securiy. The Apache manual gives you the basics. Opening up all ports is not the way to do it. Hackers are going to have a field day with your web site if you ever get it running. Stuart