Jay, That is not the problem I am having. All of our DMZ sites sit behind a Load Balance switch and all run on port 8080. Our public facing domain names\IP addresses (Public URL's) are housed on the Load Balance switch and run on port 80. When someone hits our Public url, they hit the LB switch and the switch then knows where to drop it down to based on the config for that VIP address. The end user never knows the backend web server IP because it is all handled by the LB switch. My issue was needing multiple sites to run, each on port 8080, but be able to stop and start each one individually. The have to run on port 8080 because that is what is allow to come back through our firewall to our internal BEA WL servers. John jg6789 wrote: > > Brian, > tried my.domain.com to my.domain.com:8080. doesnt work only allows > IP:PORT. > btw Cox internet out here even with a business account blocks port 80. > > ----- Original Message ----- > From: "Brian Mearns" <mearns.b@xxxxxxxxx> > To: <users@xxxxxxxxxxxxxxxx> > Sent: Wednesday, October 01, 2008 3:40 AM > Subject: Re: Running Multiple Windows Services on port 8080 > > >> As far as I know, dyndns gives you an actual DNS lookup, so when >> someone types your subdomain into their browser, it does a DNS lookup, >> and gets the IP address you gave to dyndns. That's why port numbers >> work, it's not that dyndns is listening on every port and forwarding >> based on the requested subdomain. That being the case, I don't think >> there's any way to do what you want here: DNS maps names to ip >> addresses, it doesn't know anything about ports. >> >> I'm not sure how webhop works: you can't tell it to redirect >> my.domain.com to my.domain.com:8080? Are you only able to give an IP >> address and port for the destination? >> >> If you have legitimate business needs for this site, your best bet is >> probably to just get a business account with your ISP that will >> unblock port 80. You'd probably get a static IP with the account, too, >> so you wouldn't need dyndns, you can just buy a 5$ a year domain name >> of your own. Plus, additional bandwidth. >> >> -Brian >> >> On Tue, Sep 30, 2008 at 8:05 PM, <jg6789@xxxxxxx> wrote: >>> We are using dydns too. We can append the port number, sure. that sucks >>> for >>> users though. (thats why we use webhop)maybe we should petition dyndns >>> to >>> allow the domains they hand out to be linked to an IPADDRESS:PORT >>> instead >>> of >>> just an IP. That would elminate any workarounds like webhop and suffice >>> to >>> say solve the port 80 issue with ISP's. >>> >>> ----- Original Message ----- From: "Brian Mearns" <mearns.b@xxxxxxxxx> >>> To: <users@xxxxxxxxxxxxxxxx> >>> Sent: Tuesday, September 30, 2008 2:44 PM >>> Subject: Re: Running Multiple Windows Services on port >>> 8080 >>> >>> >>>> How are you "redirecting" to the IP address? I used to use dyndns.com >>>> for my subdomain name, and I was able to append the port number with >>>> no problem. E.g., my subdomain was something like bmearns.homeip.net, >>>> so I just went to http://bmearns.homeip.net:8080. >>>> >>>> Do you not want users to see your IP address for security reasons? Or >>>> just because it's ugly and utterly forgettable? If it's for security >>>> reasons, and they're connecting directly to your site through the >>>> domain forwarding (i.e., not through a proxy), then they should be >>>> able to get your IP address anyway with a DNS lookup. >>>> >>>> -Brian >>>> >>>>>> jg6789@xxxxxxx wrote: >>>>>>> >>>>>>> John, >>>>>>> >>>>>>> We too are limited to port 8080. since our ISP blocks port 80. Have >>>>>>> you >>>>>>> ever found a work around for this? We currently have to have our >>>>>>> domain >>>>>>> [sub.domain.com] redirect to 72.x.x.x.:8080 in order for it to work. >>>>>>> Now >>>>>>> users see the ip address in the browser address bar. not good. not >>>>>>> good >>>>>>> at >>>>>>> all. >>>>>>> >>>>>>> Apache 2.2.9 >>>>>>> Linksys Gateway/Router WCG200 >>>>>>> >>>>>>> Jay >>>> >>>> --------------------------------------------------------------------- >>>> The official User-To-User support forum of the Apache HTTP Server >>>> Project. >>>> See <URL:http://httpd.apache.org/userslist.html> for more info. >>>> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx >>>> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx >>>> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx >>>> >>> >>> >>> --------------------------------------------------------------------- >>> The official User-To-User support forum of the Apache HTTP Server >>> Project. >>> See <URL:http://httpd.apache.org/userslist.html> for more info. >>> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx >>> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx >>> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx >>> >>> >> >> --------------------------------------------------------------------- >> The official User-To-User support forum of the Apache HTTP Server >> Project. >> See <URL:http://httpd.apache.org/userslist.html> for more info. >> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx >> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx >> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx >> >> > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > > -- View this message in context: http://www.nabble.com/Running-Multiple-Windows-Services-on-port-8080-tp19748920p19767167.html Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|