RE: Wide area failures?
- From: Mike Burke <MikeBurke@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 24 Apr 2008 13:30:03 -0700
Solved! The key to having the wireless LAN talk to the ethernet LAN is to use
a trusted tunnel in the Sonicwall. All the rest works out fine after that.
--
"The mind is quicker than you think!"
"Mike Burke" wrote:
I have a question about the DHCP and the DNS server:.
Assume a company running their own DNS on a windows 2003 server.
The Website, e-mail, terminal server and application server are all working
correctly.
There are other locations in other States, connected through a Sonicwall at
each location via VPN. All sites are connected to the pipe through T1 lines.
The Sonicwall is mapped to public static IP addresses (outside) and private
IP networks inside. Most of the systems on the private networks are given
static class C private Ip addresses, but on different subnets for each State.
The Wireless network is mapped internally to another private netowork, not
the same as the ethernet network, by Sonicwall design. The computers
attaching to the wireless network are given the same IP addresses if their
MAC address is on file, otherwise they are assigned addresses in a specific
range as needed. There are no problems with any nodes on the ethernet,
everything works fine.
Problem: Even though the wireless clients have their settings configured to
bring their printers forward, the printers are not visible on the network.
Problem: DHCP clients are reachable (ping) by IP address, but not by
computer name. (Understandable, since NetBIOS is not a routable protocol.)
Most of the time, putting an entry in the "hosts" and "lmhosts" files makes
the computers visible.
Scenario Question: We want to make all the computers respond to a FQDN.
Presumably we can add a route and/or the computers will broadcast their
availability to the DNS server when they come on line, but how about the
laptops with range assigned IP addresses? How does someone come in, connect
his laptop to the wireless LAN, get assigned an IP address, and still become
a host on the domain? Will a "hosts" entry of domain name to 127.0.0.1 be
enough?
If you've read this far, thank you for your patience. If you can direct me
to info about how this works I will be very grateful.
Thanks,
Mike
--
"The mind is quicker than you think!"
- Follow-Ups:
- Re: Wide area failures?
- From: Ace Fekay [MVP]
- Re: Wide area failures?
- References:
- Wide area failures?
- From: Mike Burke
- Wide area failures?
- Prev by Date: subnets/reverse lookup
- Next by Date: Re: Yet another multisite VPN DNS question!
- Previous by thread: RE: Wide area failures?
- Next by thread: Re: Wide area failures?
- Index(es):
Relevant Pages
|
