Re: connect XP pro to domain

"Bonno Bloksma" wrote:

Hi,

The Server01 has 1 NIC card so I have connected that to port 2 on the
switch and I have also connected the wireless router using ethernet to the
uplink port for the switch and then plugged my 2 XP pro computers to the
switch using the available ports.

Here you have probably started to introduce a NAT problem.
Are you sure you want the server and the XP machine on different networks?
The dhcp request will not travel through the router. Make sure you
understand ip-netwoking and routing.

1st connect everything to the LAN ports, don't use the WAN port. That way
you will have created ONE network.
Make sure the server has an IP numer which is NOT provides by the DHCP
server to another machine.

I went through to system properties-change- join to domain- entered domain
name- then a box came up whereby I had to enter a username and password
and I entered the user details I had created on Server01 but I keep
getting wrong username or bad password.

First make sure you have a correct ip connection. Make sure a simple ping
command works. After that you can look at the next level.

--

Groetjes,
Bonno Bloksma



This has nothing to do with the NAT at the moment. Misheck, just follow this
setting and you will be all set:

Server--------
|
XP1-----------|--------Switch----------->Router----------->Internet
|
XP2-----------

1. Static IP address for the server. Use the server as a DCHP & DNS server
2. Configure XP machines to obtain DHCP address from the server
3. Make sure you can ping the server from those XP machines by name and vice
versa.
4. Join those XP boxes to the domain using either domain administrator
account or any account belong to domain admin group. As PAJ has mentioned
above, use this format for user name: contoso\administrator. You should be
able to join the domain by then.
5. Disable your wirless router DHCP
6. Connect your router's LAN port to the switch. Most of the switches
nowaday have autosensing function, therefore you may not even need to use a
crossover cable. If that is not the case, then just use the uplink port with
a straight cable.
7. Configure your server DHCP scope to include the router's internal static
IP address as the gateway.
8. Renew the IP addresses for the XP boxes to make sure they get the new
gateway information.

Let's us know if you still have problem.
.

Relevant Pages

  • Re: Attaching DHCP Server Management to Fixed TCP Port
    ... there may be enough ways to access ur dhcp server via vpn. ...   ... management of the DHCP server by machines behind our firewall only. ... The most secure solution is one that locks the DHCP Server management port ...
    (microsoft.public.windows.server.networking)
  • Re: Regarding dhcp client problem
    ... I have captured the packet information from the device. ... win2k dhcp server sends ... But the dhcp client in the device is not receiving the offer at ... User Datagram Protocol, Src Port: bootpc, Dst Port: bootps ...
    (comp.arch.embedded)
  • Re: 802.1x authentication issue
    ... There was nothing wrong with the switch port, ... Yes, we are using IAS for PEAP authentication, I analyzed IAS logs but didn't ... I ended up switching the machine to a NON .1x port, disjoining the Domain, ... If the machine has an APIPA address it means it can't contact the DHCP ...
    (microsoft.public.windows.server.networking)
  • Re: Windows Server 2003 DHCP server - Does not release IP Addresses
    ... on the SWITCH or the ROUTER. ... the clients will not know which server to go for DHCP REQUEST. ... And, if that Switch had some issues, how will the other DHCP server ... This error is usually received when the client booting up via PXE is ...
    (microsoft.public.windows.server.general)
  • Re: Home Network
    ... You have a router you say is running DHCP and is routing between the ... How are you "connecting" to your ftp server, ... Are you using host files for name ... server connected to a switch, a cable modem/router with dhcp also ...
    (microsoft.public.windowsxp.general)