Re: help with server config

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Wireless cards can complicate a things a bit in that often the wireless
connection does not initialize fast enough to authenticate the computer in
the startup process [both computer and user authenticate to the domain].
However by default Windows XP/2000/2003 will allow cached logons to the
domain as long as you have successfully logged onto the domain at least once
[such as when joining it] . In such case what usually happens is that the
user can only logon to the local computer and not authenticate to domain
resources until a domain controller can be contacted which it usually can be
shortly after the wirless card establishes network connectivity. This
usually is not a big problem unless you are using 802.1X and EAP-TLS
wireless authentication which requires a computer and user certificate for
the client computer. In your case just make sure you have at least WEP
enabled and if possible use WPA instead as WEP is fairly weak unless keys
are changed fairly regularly. -- Steve


"Eddie Jefferson" <edsa@xxxxxxx> wrote in message
news:d52rv1$qo0$1@xxxxxxxxxxxxxxxxxxxxxxxx
> Forgot to mention Steven that I have a netgear DG834G wireless router (all
> in one) and am using 1 PCI wireless NIC in the server. I am going to use
> wireless PCI cards in the XP clients. Will this cause a problem?
>
> "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxx> wrote in message
> news:OnEU45lTFHA.1148@xxxxxxxxxxxxxxxxxxxxxxx
>> While it is possible to use NAT on a domain controller I strongly
>> recommend that you do not have multiple network adapters in a domain
>> controller as it can cause an assortment of problems with domain clients
>> finding the proper IP address of the domain controller to contact Active
>> Directory and for "network browsing" via My Network Places as your domain
>> controller will also be the domain master browser.
>>
>> Assuming you are using cable/dsl your best solution is to get a NAT/PAT
>> router device to connect to the cable/dsl modem an obtain tcp/ip info
>> from your ISP. Disable DHCP on that device and use it as the default
>> gateway for your network. These devices are made by the likes of Netgear,
>> D-Link, Linksys, etc if you do not know what they are and available at
>> Best Buy, Amazon, and such for a very reasonable price. Consider getting
>> a wireless enabled one if you ever thing you will want wireless access
>> and you can disable wireless access until then.
>>
>> http://www2.newegg.com/home/Network.asp -- link to networking devices
>>
>> Then configure your domain controller to use DHCP for domain clients. To
>> configure dns for domain name resolution and internet name resolution
>> configure dns on the domain controller to either forward to your ISP dns
>> server or use "root hints". You want your domain controller to point to
>> itself as its preferred dns server and the domain computers must point
>> ONLY to the domain controller as their preferred dns server [which can be
>> done via DHCP scope] . The link below explains this more. --- Steve
>>
>> http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382
>>
>> "Eddie Jefferson" <edsa@xxxxxxx> wrote in message
>> news:d52jmf$nqf$1@xxxxxxxxxxxxxxxxxxxxxxxx
>>> Hello All
>>>
>>> Can anyone help me to set up my 2003 server?
>>>
>>> I have 1 2003 server DC and several windows XP clients.
>>>
>>> I would like to set up my server so that all the XP clients can
>>> authenticate through the server and access the internet.
>>>
>>> DHCP is installed.
>>>
>>> I have the server set up with a static IP address from my ISP. The
>>> network settings on the server are as follows: -
>>>
>>> IP address 195.137.89.162
>>> Subnet mask 255.255.255.252
>>> Gateway 195.137.89.161
>>>
>>> DNS 1 194.106.56.6
>>> DNS 2 194.106.33.42
>>>
>>> Can I have the server set up with these settings and issue IP details to
>>> the clients using DHCP? Will I have to set up a proxy server to do
>>> this?
>>>
>>> Its the first time I've tried this so I would be grateful for any help.
>>>
>>> thanks
>>>
>>> ed
>>>
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Create a wireless domain?
    ... > windows server and create a domain controller. ... For details on this authentication method, ... Authentication for IEEE 802.11 Wireless Network Access" ...
    (microsoft.public.windows.server.networking)
  • CIFS Authentication in AD 2003
    ... We have a HPUX server running FacetWin on ... authenticate domain users looking to access its resources. ... Everything was working perfectly when our main domain controller was ...
    (microsoft.public.windows.server.active_directory)
  • question about IAS and PEAP MS-CHAP V2 (wireless authentication)
    ... MS-CHAP V2, and wireless. ... I am using MS-CHAP V2 to authenticate PDAs ... AD credentials to authenticate the clients. ... states that we have to install the server certificate onto the device. ...
    (microsoft.public.security)
  • MS-CHAP V2 and server certs
    ... MS-CHAP V2, and wireless. ... I am using MS-CHAP V2 to authenticate PDAs ... AD credentials to authenticate the clients. ... states that we have to install the server certificate onto the device. ...
    (microsoft.public.security)
  • Re: How to know which Active Directory Server Ive logged on?
    ... server is the user's exchange home server. ... Users from a certain domain can authenticate against every ... location then a user is authenticated by a domain controller covering ...
    (microsoft.public.win2000.active_directory)