Technically, it should be 172.16.X through 172.31.X (meaning 172.16.X, 172.17.X, 172.18.X, ...) instead of just 172.16.X :-)
Mike BJ Freeman wrote: > 10.x > 172.16.X > 192.168.X > http://tools.ietf.org/html/rfc1918 > > [EMAIL PROTECTED] sent the following on 11/7/2007 10:44 AM: >> BJ >> >> Is it all 10.X addresses or just 10.0.x? Ditto with 192.168.X >> >> Skip >> >> -----Original Message----- >> From: BJ Freeman [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, November 07, 2007 10:18 AM >> To: user@ofbiz.apache.org >> Subject: Re: I've seen this asked but not answered >> >> >> understand that a 10.X.x.x address is a private address to a network >> node. if the computer trying to access this box is not on this network >> it will not see it. >> >> Also you should be using a Router that is on this node, take a public IP >> and route to the box's 10.142.53.1010 >> >> Case Torres sent the following on 11/7/2007 7:09 AM: >>> Skip, >>> >>> Thanks so much for your quick reply. I have to have this up and running by >>> the end of the week :-{ >>> >>> I can ping the box. >>> When attempting a connection, I'm getting a "Connection has timed out. The >>> server at 10.142.53.10 is taking too long to respond." >>> >>> We also have a WAN address that does the same thing. From your response, >> it >>> sounds as though the problem might lie in the network configuration. I'll >>> check this out further. >>> >>> Thanks again, Case >>> >>> -----Original Message----- >>> From: Skip [mailto:[EMAIL PROTECTED] >>> Sent: Tuesday, November 06, 2007 11:42 AM >>> To: user@ofbiz.apache.org; [EMAIL PROTECTED] >>> Subject: RE: i've seen this asked but not answered >>> >>> Case >>> >>> You dont need to make any of these changes you are making to the Ofbiz >>> setup. Put them all back the way they were originally setup. There are >> no >>> problems there (at least in the area you are concerned with). >>> >>> Then, assuming the machine running ofbiz is on 10.142.53.10 and you are on >>> 10.142.53.11, you should be able to connect just fine with the address you >>> have below. >>> >>> If you are on a different subnet, be sure you have access to the subnet >> the >>> ofbiz server is on. >>> >>> You can do this: >>> >>> ping 10.142.53.10 >>> >>> or >>> >>> tracert 10.142.53.10 (Windows) >>> traceroute 10.142.53.10 (linux) >>> >>> Assuming the machine sitting at 10.142.53.10 is named Ofbizserver, you >>> should also be able to: >>> >>> ping Ofbizserver (on a LAN) >>> >>> or >>> >>> ping Ofbizserver.domain.com (on the internet). (eg. ping www.yahoo.com) >>> >>> so long as there is a DNS somewhere that knows about it. >>> >>> If you can't ping it, you can't connect. You may need to specify a >> gateway >>> from the machine you are trying to connect from to the machine you are >>> trying to connect to. >>> >>> Skip >>> >>> -----Original Message----- >>> From: Case Torres [mailto:[EMAIL PROTECTED] >>> Sent: Tuesday, November 06, 2007 11:16 AM >>> To: user@ofbiz.apache.org >>> Subject: RE: i've seen this asked but not answered >>> >>> >>> Jonathan, >>> >>> Thanks for your quick reply. >>> >>> Are you saying I don't need to make any changes in any files, anywhere? >>> >>> I've tried just typing in the machines WAN and LAN IP address in the >>> browser, for instance, https://10.142.53.10:8443/webtools/control/main >>> >>> The process times out when trying to connect to the WAN IP address >>> And >>> The connection is refused when attempting to connect to the LAN IP >> address. >>> I've also tried changing the 127.0.0.1 to the new ip in >> ofbiz_containers.xml >>> file. >>> >>> So, I'm thinking I need to makes some changes to various files. >>> >>> Thanks again, Case >>> >>> >>> >>> -----Original Message----- >>> From: Jonathon -- Improov [mailto:[EMAIL PROTECTED] >>> Sent: Monday, November 05, 2007 6:51 PM >>> To: user@ofbiz.apache.org >>> Subject: Re: i've seen this asked but not answered >>> >>> Case, >>> >>> As long as your OFBiz is deployed on the server you want to access, you >> can >>> access OFBiz via any >>> names that server has. >>> >>> It can be 127.0.0.1 (if you're accessing from the OFBiz server itself), or >>> whatever IP addresses >>> the OFBiz computer has. Or even any domain names assigned to that machine. >>> >>> Your question becomes more complex if you want to PREVENT users from using >>> all names to the server >>> except for one. Say you just want users to access OFBiz via >>> http://public.site.ofbiz:8443/webtools . >>> >>> Note that you can use some "<host>" element (IIRC) to do virtual hosts. >>> >>> Jonathon >>> >>> Case Torres wrote: >>>> I know this is a real novice question. >>>> I want to change the 127.0.0.1 to a different ip address. >>>> So I can connect http://myipaddress:8443/webtools/contol/main. >>>> >>>> Where do I make this happen? >>>> >>>> I looked thru the documentation but didn't find the answer. And I looked >>>> thru this forum's postings and it was asked in feb but there was no >>> answer. >>>> I tried changing 127.0.0.1 to my ip in ofbiz-containers.xml but it didn't >>>> work. >>>> >>>> Thank you much, Case >>>> >>>> >>>> Case Torres >>>> [EMAIL PROTECTED] >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> No virus found in this incoming message. >>>> Checked by AVG Free Edition. >>>> Version: 7.5.503 / Virus Database: 269.15.21/1110 - Release Date: >>> 11/4/2007 9:37 PM >>> >>> >>> >>> >>> >> >> >> -- Millcreek Systems, Inc. P.O. Box 9835 Salt Lake City, Utah 84109 Phone: 801.649.4903 Skype: millcreeksys (http://millcreeksys.com/skype/)
