PDA

View Full Version : How do I map address to ip address


myjobs98
Mar 4, 2010, 04:45 AM
Hello

We have installed web application in our organization. To access it, just type in the browser server name that host that application (e.g. http:\\learn) and it will ask you about user name/pass to give you access. This works in departments that have same default gateway

The problem when we tried to access it from our branches which are in other cities and linked to out data center using VPN, it didn't recognize the address (http:\\learn). The browser error "The address is not valid".
<<<But they can ping the server IP address>>>

What configuration do we need to include in router in order that clients in other branches recognize the address?

IPs in data center
192.22.7.?

IPs in our dept
192.22.4.?

The above are in same "default gateway"

IPs in branches
1st branch: 192.22.15.?

Thanks in advance

Curlyben
Mar 4, 2010, 04:51 AM
Make sure the name is mapped to an IP in DNS.
DNS management on your DC will replicate this information throughout the domain.
Just add a new host(a) with the appropriate information.

Like this:

sitename 192.22.x.x

myjobs98
Mar 4, 2010, 04:58 AM
Thanks for your answer.

We don't have DNS in our DC. For internet we put DNS address for ISP.

Curlyben
Mar 4, 2010, 05:01 AM
Are you running active directory on your domain ?

myjobs98
Mar 4, 2010, 05:10 AM
Currently no
But in the coming weeks we will.

But we can't wait till we lunch the Active diretory

Curlyben
Mar 4, 2010, 05:23 AM
The quick and dirty way would be to add an entry to the Hots file directing site traffic to the specified IP.

myjobs98
Mar 4, 2010, 05:29 AM
You mean host file?

Actually this is not quick way. Because we need to do that in around 300 clients (this is just the beginning as the number of users will increase).

That's why I prefer to do something in the routers only which means one device in each branch rather than around 50 PC in a branch.

Thanks

Curlyben
Mar 4, 2010, 05:32 AM
Yep I did mean hosts.

Therein lies your problem.
With the "correct" infrastructure (active directory) this would have been a snap.

If you are dealing with that number of machines, just tell them to us the IP.