Accessing LAN computer with external IP address

[Guest]

My network network has computers with ip addresses 192.168.0.xxx with
255.255.255.0 subnet mask. One of the internal computers on network is
visible to outside world at the fixed ip address. The D-Link DI624 router
routes the traffic from outside world to the lan computer for specific ports.
I can access this local computer with 192.168.0.100 addrerss. I can access
the computer whenever I am outside office using the 'outside world' address.
However, I want to access it with the same 'outside world' address from
inside lan. How do I configure my windows XP computer so that all requests to
the 'outside world' address are directed to my local network, and I get
consistent access to the computer from inside or outside the office? I have
only 1 fixed IP address assigned to my office and would like a network
configuration solution without any other hardware/service additions.

 

[Lanwench [MVP - Exchange]]

In

My network network has computers with ip addresses 192.168.0.xxx with
255.255.255.0 subnet mask. One of the internal computers on network is
visible to outside world at the fixed ip address. The D-Link DI624
router routes the traffic from outside world to the lan computer for
specific ports. I can access this local computer with 192.168.0.100
addrerss. I can access the computer whenever I am outside office
using the 'outside world' address. However, I want to access it with
the same 'outside world' address from inside lan. How do I configure
my windows XP computer so that all requests to the 'outside world'
address are directed to my local network, and I get consistent access
to the computer from inside or outside the office? I have only 1
fixed IP address assigned to my office and would like a network
configuration solution without any other hardware/service additions.

Are you referring to remote desktop, perchance? You haven't described what
'access' means - nor which ports are in use.
Are you using AD, and/or do you have an internal DNS server?

I do find this an odd request (and I would use the computer's name, not its
IP address, internally - as well as using an A record for my public DNS that
pointed at the correct public IP, for external access). Is it just for ease
of use?

 

[Guest]

Some more specifics:
1. The computer on LAN that has access from outside has a DNS name and users
access it with the domain name instead of the address. The computer hosts
dynamic web pages using SQL server and ASP.
2. When I access using domain names from inside the LAN, the DNS server
resolves the IP address. However, when attempt to access the IP address is
made, I get not found as my LAN is looking for the address in the 'outside'
world.
3. I do not have internal DNS server. Basically, all my computers connect to
the D-link router.

Ideally, I would like my D-link router to direct the mydomainname.com
request to internal network when made from inside the LAN. But there is no
provision for that.

So, I am looking for some setting in Windows XP where I can say
mydomainname.com= 192.168.0.100 when I am inside the LAN. This setting will
be removed when I am on road. Are there any better ways to achieve seamless
access to the web page located on my LAN machine using public domain
name/address.

 

[Guest]

you are making it very complex.
What I understand from your is that you want to access the computer (where u
r runing asp pages) both from outsie and inside.

From outside you use the domain name but from from inside you can't.

From inside don't type the domain name on the browser, better type the
computer name e.g. http://computername and the default wesbite shall work as
it works from outside. outside=internet

 

[Guest]

Hello,
You understood the problem right. At present, I am doing just as you
suggested. However, the asp access is actually made programatically, so I
have to edit the web page address,making it a time consuming process to
change. I am looking for a way in windows networking, to direct all traffic
to IP address to my web page to internal computer when I am on LAN. When I am
inside LAN, I will issue that routing command. When I am outside, I will not.