Small routing issue

Hi,


I have a problem which I am quite sure off is some simple routing oversight
of mine, but I haven't find the solution yet.

Our network has 3 zones, the LAN (192.168.168.0 / 24), the DMZ (192.168.0.0
/ 24) and our one fixed WAN IP (123.123.123.123).
In the DMZ is our webserver (B2B part, the public part is hosted by the
ISP).
When I am at home I can access the B2B part perfectly (using
http://123.123.123.123/B2B). However when I am connected to the company LAN
I cannot access it, unless I use the DMZ private IP
(http://192.168.0.3/B2B).

Because a picture says more than a thousand words I uploaded one to my
website: http://users.pandora.be/obsession200...ingProblem.jpg
Someone here have the solution?

thanks,

David

PS: I know that if our DNS host adds an A record for b2b.companyname.com, I
can use our local DNS or computers hosts file to solve it, but at the moment
that's not an option.

Depends on which router you have, you may have a commend point the public IP 123.123.123.123 back to 192.168.0.3. Or you may want to use tracert command to find where is 123.123.123.123. go.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
"David" <David-(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Hi,


I have a problem which I am quite sure off is some simple routing oversight
of mine, but I haven't find the solution yet.

Our network has 3 zones, the LAN (192.168.168.0 / 24), the DMZ (192.168.0.0
/ 24) and our one fixed WAN IP (123.123.123.123).
In the DMZ is our webserver (B2B part, the public part is hosted by the
ISP).
When I am at home I can access the B2B part perfectly (using
http://123.123.123.123/B2B). However when I am connected to the company LAN
I cannot access it, unless I use the DMZ private IP
(http://192.168.0.3/B2B).

Because a picture says more than a thousand words I uploaded one to my
website: http://users.pandora.be/obsession200...ingProblem.jpg
Someone here have the solution?

thanks,

David

PS: I know that if our DNS host adds an A record for b2b.companyname.com, I
can use our local DNS or computers hosts file to solve it, but at the moment
that's not an option.

Some devices don't support "hair-pinning" (going out an interface and then
back in). Some devices support alias's or you can just change your DNS
record to point to your DMZ address.


"David" <David-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
>
> I have a problem which I am quite sure off is some simple routing
oversight
> of mine, but I haven't find the solution yet.
>
> Our network has 3 zones, the LAN (192.168.168.0 / 24), the DMZ
(192.168.0.0
> / 24) and our one fixed WAN IP (123.123.123.123).
> In the DMZ is our webserver (B2B part, the public part is hosted by the
> ISP).
> When I am at home I can access the B2B part perfectly (using
> http://123.123.123.123/B2B). However when I am connected to the company
LAN
> I cannot access it, unless I use the DMZ private IP
> (http://192.168.0.3/B2B).
>
> Because a picture says more than a thousand words I uploaded one to my
> website: http://users.pandora.be/obsession200...ingProblem.jpg
> Someone here have the solution?
>
> thanks,
>
> David
>
> PS: I know that if our DNS host adds an A record for b2b.companyname.com,
I
> can use our local DNS or computers hosts file to solve it, but at the
moment
> that's not an option.
>
>

"David" <David-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> When I am at home I can access the B2B part perfectly (using
> http://123.123.123.123/B2B). However when I am connected to the company
LAN
> I cannot access it, unless I use the DMZ private IP
> (http://192.168.0.3/B2B).

That is the way it is supposed to be. Neteng has your answer. It is a
limitation in NAT,...it creates a situation where both the source ans
destination MAC Address in the Layer2 packet are the same address,...which
isn't functionally possible, so it fails.

Had this been performed with a proxying service, such as ISA Server's "Web
Publishing" facility within the Web Proxy Service this would function
because NAT is not being used

The following article explains the issue. It is found about half way through
the article under the heading "Normal NAT behavior" and more specifically
under the heading "14120 Errors".

14120 Errors; Discussion and Solution
http://www.isaserver.org/articles/14..._Solution.html


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------