Problem reaching our 2k3 server from within the Intranet

Hello.

I'm quite sure our problem is due to a network configuration problem,
but I thought I'd give it a try asking here.

We are running a computing backend on a Windows Server 2003 at
192.168.0.x; Our network is behind a router, which itself is connecting
to the internet through gateway that belongs to the company that owns
the building.
Our (static) IP 62.x.x.x is mapped to our building internal IP 10.50.x.x
where our router is listening. The router forwards the specific ports to
our server.

The thing is that we can reach our server from WAN without any problem,
but whenever we try to connect to our static IP 62.x.x.x we don't get
any connection.

Our router allows us the configuration of "virtual" computers; When we
create one, effectively mapping 62.x.x.x to 192.168.x.x we are able to
reach the server via the static IP from WAN and from LAN, but the server
isn't able to connect to the internet anymore.
This is driving me nuts.

Any ideas?

Best regards from Berlin,
Markus

--
To answer via mail, please remove the .hates-spam part from the address.
A crypto key is available.

HI,
> The thing is that we can reach our server from WAN without any problem,
> but whenever we try to connect to our static IP 62.x.x.x we don't get any
> connection.
So, then i might not be able to telnet your router a configure that one for
my purposes ?!
Or is there any service running, i can use for myself ?
;-) Except for a ping.

> Our router allows us the configuration of "virtual" computers; When we
> create one, effectively mapping 62.x.x.x to 192.168.x.x we are able to
> reach the server via the static IP from WAN and from LAN, but the server
> isn't able to connect to the internet anymore.
> This is driving me nuts.
May be your server is not up to be used as a surfing machine; may be someone
forgot to setup the default route.
Or the server sits in a demilitarised zone and its gateway is that one to
the internal one.

Who knows ?
jk