Wide area failures?



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!"
.



Relevant Pages

  • Re: Cannot browse or open shared printers or server on sbs 2003 from client pc
    ... i think the network problem has taken a different turn. ... meanwhile if i access the mapped drives to the server which we setup in the ... my thought now is what is the update mechanism for the printers from the ... I understand the issue to be: client computers can ...
    (microsoft.public.windows.server.sbs)
  • Re: List of servers in this workgroup is currently not available.
    ... Computer description appears before the computer name in the My Network ... Microsoft CSS Online Newsgroup Support ... <recently installed a D-Link print server with a reserved IP. ... <As soon as I uninstalled the print server and rebooted the computers, ...
    (microsoft.public.windows.server.sbs)
  • Help with 070-217
    ... The network contains 25,000 computers. ... single Windows 2000 domain named research.contoso.com. ... Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)
  • RE: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)