New Posts New Posts RSS Feed: BOS Port and IP Forwarding
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

BOS Port and IP Forwarding
 Post Reply Post Reply
Author
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
Vonzkie View Drop Down
Senior Member
Senior Member
Avatar

Joined: 01-Aug-2011
Location: PH
Posts: 133 		Post Options Post Options   Quote Vonzkie Quote  Post ReplyReply Direct Link To This Post Topic: BOS Port and IP Forwarding
    Posted: 06-Jun-2012 at 11:06pm
Hi,

If we didn't fill the ServerPort property on the configuration, what would be the default port of the BOS? Is it Port 80?
Another, example we have a public address of 99.99.99.99 that directs to a local ip of 192.168.0.15 and the BOS is really located at 192.168.0.15, how can we deal with that in our client or server settings?

Thanks,
Von
Back to Top
DenisK View Drop Down
IdeaBlade
IdeaBlade


Joined: 25-Aug-2010
Posts: 715 		Post Options Post Options   Quote DenisK Quote  Post ReplyReply Direct Link To This Post Posted: 07-Jun-2012 at 3:08pm
Hi Von,

If we didn't fill the ServerPort property on the configuration, what would be the default port of the BOS? Is it Port 80?

This depends on where you're deploying your BOS. If you're deploying on your own managed IIS, and you haven't changed its default setting, then yes, the default port will be 80.

Another, example we have a public address of 99.99.99.99 that directs to a local ip of 192.168.0.15 and the BOS is really located at 192.168.0.15, how can we deal with that in our client or server settings?

You don't configure this in your client or server config. Only the router is involved in directing this. So if you have configured your router to direct any request from the public ip to the local ip, everything should work.
Back to Top
Vonzkie View Drop Down
Senior Member
Senior Member
Avatar

Joined: 01-Aug-2011
Location: PH
Posts: 133 		Post Options Post Options   Quote Vonzkie Quote  Post ReplyReply Direct Link To This Post Posted: 07-Jun-2012 at 4:33pm
Hi Denis,

Actually that's what we did, we have two Web Project, one is a Administration Site and the BOS.
The client application is a Windows Form Application that access some service of the Administration Site and uses Devforce in data manipulation.
We successfully access the services in the Administration Site (native WCF service with EF4 Code First) but we we're not able to connect to the BOS.
Both sites resides on the same host. 192.168.0.15

Example:

http://99.99.99.99/AdminPortal.Web/Services/SampleService.svc can be accessed publicly and we were able to connect to the service
http://99.99.99.99/BusinessObjectServer.Web/EntityServer.svc can be accessed publicly but I don't know why we can't initialize our EntityManager using this kind of Setup

Can you shed some light one what we're doing wrong here?

Note that without this IP Forwarding mechanism, we don't experience problem in connecting to BOS.

Regard,
Von
Back to Top
DenisK View Drop Down
IdeaBlade
IdeaBlade


Joined: 25-Aug-2010
Posts: 715 		Post Options Post Options   Quote DenisK Quote  Post ReplyReply Direct Link To This Post Posted: 08-Jun-2012 at 12:24pm
Hi Von,

We need more information in order to debug this. Could you provide us with the following?

1. The exception and stack trace you're getting when you're trying to initialize the EM.

2. The client and server DevForce debug logs. See http://drc.ideablade.com/xwiki/bin/view/Documentation/log in case you need more info.

3. A Fiddler session with DevForce extension installed. http://drc.ideablade.com/xwiki/bin/view/Documentation/fiddler
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down