Wireless lans & exchange / dns etc.

I'm trying to set up a domain on the inside of a wireless (cable) network.
My goal is to have my own exchange server to handle my e mails etc with owa.
My problem is however, i'm using w2k server & exch 5.5, on the inside of a
wireless network. At the moment the router (linksys) provides dhcp & dns
resolution, should the server be setup to provide dhcp instead of the
router, then in turn the router be given the static addresses?

Also where should the dns resolution be coming from? is it just the case of
aiming the server at the firewalls ip?

Are there any good sites i can go to, to look at similar configurations?

TIA Stu

Hi,

It doesn't matter which device or server will give out IP addresses to the
client. Still there are few things to pay attention to:
* Active Directory relies on DNS as source of information. Usually AD
servers will also be DNS servers. It will make your life easier if you
assign your AD and DNS server a static IP address
* Once you have your AD setup, make sure that your domain computers (client
computer) are configured with your Active Directory server as preferred DNS
server. You can configure your DHCP device or server to give out this
information to the clients
* just like clients your AD server should point to AD DNS server for
preferred DNS server (on server you can enter e.g. 127.0.0.1 as preferred
DNS server IP address).
* now for your clients to be able to resolve the addresses on the internet
open DNS MMC on your active directory server and right click on your server
name. Select properties and click on Forwarders tab. Add IP address of your
ISP's DNS server. Now if your client will query AD DNS for www.cnn.com the
request will be forwarded to your ISP's DNS...

Note, that if any of the domain members will have your ISP's DNS set as
preferred DNS instead of your internal AD DNS, they will either not work or
clients will experience long logon times...

I hope this helps,

Mike

"Stu" <(E-Mail Removed)> wrote in message
news:eXf%(E-Mail Removed)...
> I'm trying to set up a domain on the inside of a wireless (cable) network.
> My goal is to have my own exchange server to handle my e mails etc with
> owa. My problem is however, i'm using w2k server & exch 5.5, on the inside
> of a wireless network. At the moment the router (linksys) provides dhcp &
> dns resolution, should the server be setup to provide dhcp instead of the
> router, then in turn the router be given the static addresses?
>
> Also where should the dns resolution be coming from? is it just the case
> of aiming the server at the firewalls ip?
>
> Are there any good sites i can go to, to look at similar configurations?
>
> TIA Stu
>

On Sun, 5 Dec 2004 21:22:50 -0000, "Stu" <(E-Mail Removed)>
wrote:

>I'm trying to set up a domain on the inside of a wireless (cable) network.
>My goal is to have my own exchange server to handle my e mails etc with owa.
>My problem is however, i'm using w2k server & exch 5.5, on the inside of a
>wireless network. At the moment the router (linksys) provides dhcp & dns
>resolution, should the server be setup to provide dhcp instead of the
>router, then in turn the router be given the static addresses?

Yes.

>Also where should the dns resolution be coming from? is it just the case of
>aiming the server at the firewalls ip?

You want DNS pointed at the server which has your DNS records,
wherever that may be. If you don't host your own DNS externally, you
can configure an internal DNS and forward to your ISP's DNS from that.
See the DNS groups for more info.

Jeff

Thanks for that guys,
i have one further question, which is as a result of you both talking about
dns.
my cable isp, will not allow a static ip address, however my www site's isp
allow for custom ip's to be used, and will allow me to redirect my domain
names ip to one i can obtain from dyndns.com.

So which will be the best ip to use, one from my cable company or the one
that is going to be a custom address? As i said earlier, i'm looking to run
exchange at home, and have pop3 mail coming from my www domain name to the
exchange box.

TIA




"Stu" <(E-Mail Removed)> wrote in message
news:eXf%(E-Mail Removed)...
> I'm trying to set up a domain on the inside of a wireless (cable) network.
> My goal is to have my own exchange server to handle my e mails etc with
> owa. My problem is however, i'm using w2k server & exch 5.5, on the inside
> of a wireless network. At the moment the router (linksys) provides dhcp &
> dns resolution, should the server be setup to provide dhcp instead of the
> router, then in turn the router be given the static addresses?
>
> Also where should the dns resolution be coming from? is it just the case
> of aiming the server at the firewalls ip?
>
> Are there any good sites i can go to, to look at similar configurations?
>
> TIA Stu
>

Hi,

One option would be to use NAT device (router, firewall) and private IP
addresses behind NAT device (e.g. on LAN).
In this scenario you could use e.g. 192.168.0.0 IP static addresses range
for your AD and other computers on LAN. Still on the outside you would use
public IP addresses assigned by your ISP.

Mike

"Stu" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks for that guys,
> i have one further question, which is as a result of you both talking
> about dns.
> my cable isp, will not allow a static ip address, however my www site's
> isp allow for custom ip's to be used, and will allow me to redirect my
> domain names ip to one i can obtain from dyndns.com.
>
> So which will be the best ip to use, one from my cable company or the one
> that is going to be a custom address? As i said earlier, i'm looking to
> run exchange at home, and have pop3 mail coming from my www domain name to
> the exchange box.

The other thing you problably should check on is wether your ISP allows port
25 (SMTP) to/from clients.

Some ISPs block this port to prevent spammers and if you run an email server
from home both your outbound and inbound access for the server could be
blocked.

Mike

"Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi,
>
> One option would be to use NAT device (router, firewall) and private IP
> addresses behind NAT device (e.g. on LAN).
> In this scenario you could use e.g. 192.168.0.0 IP static addresses range
> for your AD and other computers on LAN. Still on the outside you would use
> public IP addresses assigned by your ISP.
>
> Mike
>
> "Stu" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Thanks for that guys,
>> i have one further question, which is as a result of you both talking
>> about dns.
>> my cable isp, will not allow a static ip address, however my www site's
>> isp allow for custom ip's to be used, and will allow me to redirect my
>> domain names ip to one i can obtain from dyndns.com.
>>
>> So which will be the best ip to use, one from my cable company or the one
>> that is going to be a custom address? As i said earlier, i'm looking to
>> run exchange at home, and have pop3 mail coming from my www domain name
>> to the exchange box.
>
>