Joint WinXP PC to Win3k PC Active Domain

I just setup my pc with Win3k Ent Edition and running Active Domain while my client pc connection to Win3k pc with 1 NIC on each pc using crossover cable.

The problem is I couldn't join to Win3k domain which I created. I tried to ping from 1 NIC to another but end up with no response. Just a question, client pc can't join to Win3k domain using this way? If not, any solution for it to solve the problem?

On the Win3k pc, I have created a user and computer at the active directory users and computers. The Win3k also running DHCP server which there's extra NIC which connected to my ADSL connection. That means on the Win3k pc has 2 NICs. Anyone willing to help me with my problem?

Some of these things should be checked to get communication between the two computers:

1. Set the client to a workgroup like the domain name. For example, if the domain name is domain.com, set the client to the workgroup domain (without the .com).

2. Remove or disable any antivirus software (including the XP built-in Internet Connection Firewall).

3. Configure TCP/IP Protocol correctly. Set the Ip addresses so that they are like the ones shown below:
server IP: 192.168.0.1
server subnet: 255.255.255.0
server default gateway: (blank)
server DNS server: 127.0.0.1

client IP: 192.168.0.2
client subnet: 255.255.255.0
client DNS server: 192.168.0.1
client default gateway: 192.168.0.1

After this, you should be able to ping OK. From both compters, try pinging 192.168.0.1 and 192.168.0.2. If you can successfully ping from both computers, then the client computer should be able to join the domain (don't forget that the client must be running 2000 Pro or XP Pro).

Open the System applet from the Control Panel and click Computer Name tab. Click the Change button and select Domain and then enter in the domain name, such as domain.com. Click OK - if it works then fine - if it doesn't then what error message do you get?

To share the Internet (as long as you have the default gateway set on the client as shown above), you need to right-click the ADSL connection in Network Connections in the control panel and select Properties. Click the Advanced tab and enable Internet Connection Sharing. This should just work.

HTH,

Edwin

I just did all those but still couldn't ping each other.
Is there any problem with my Win3k settings?
BTW, this is my Win3k setting -
Primary suffix of computer : abc.local
NetBios Computer Name : abc-server
Does this setting related to current problem?

Even though I remove running DHCP and my server role only Active Domain enabled but it is still not working. Any idea?
BTW, I'll check the crossover cable to make sure that not faulty later on.

I just tested the crossover cable at other PCs and it is working. I don't think that can be the NICs problem since I'm able to ping the IP which belongs to each PC itself.

Is there possible for me to remove the domain on the Win3k pc and create a same workgroup name for both pc. If able to ping each other then I'll create a domain again and join the client pc to the Win3k pc.

Forgot to mention my client PC running WinXP pro. BTW, do I need to update the IPv6 on my client pc if related?

Are you sure that you have set the IP addresses correctly on each machine (192.168.0.x) and there is no firewall software running (ICF, ZoneAlarm, etc.)?

Can I have a look at the IP config for each machine. Click the Start button and select Run. In the Run dialog box type "ipconfig /all > C:\ipconfig.txt" (without the quotes) and then do this on your second computer. Then include the contents of C:\ipconfig.txt in your next post.

Will show here when I reach home.
A few question :
1) Do I need to set my client's workgroup to abc.local or just abc without .local at the back?
2) Why we need to set the DNS for the Win3k to 127.0.0.1?

1. abc by itself should do just fine (no need for .local)

2. When you set up Active Directory you will have configured DNS, for translating domain names into IP addresses. The server needs to be told that the DNS server can be reached at the address 127.0.0.1 (this address is the server itself). This means that when the server needs to translate domain names to IP addresses, it knows to use itself.

Thanks.
2 more hours to go before I reach home

Windows IP Configuration
Host Name . . . . . . . . . . . . : ck-desk
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x

Family Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-C0-26-26-E5-54
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1

PPP adapter StreamYX:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 219.95.4.48
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 219.95.4.48
DNS Servers . . . . . . . . . . . : 202.188.0.133
202.188.1.5
NetBIOS over Tcpip. . . . . . . . : Disabled

That looks good for the client. Can I check the server as well?

Windows IP Configuration
Host Name . . . . . . . . . . . . : win3k-server
Primary Dns Suffix . . . . . . . : abc.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : abc.local

Ethernet adapter Local Area Connection :
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapter (10/100)
Physical Address. . . . . . . . . : 00-D0-B7-B8-44-A7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.0.2
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
Lease Obtained. . . . . . . . . . : Tuesday, March 02, 2004 9:48:35 PM
Lease Expires . . . . . . . . . . : Friday, March 05, 2004 9:48:35 PM

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ADMtek AN983 based ethernet adapter
Physical Address. . . . . . . . . : 00-08-A1-58-F5-7A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1

PPP adapter Streamyx:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 219.95.10.248
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 219.95.10.248
DNS Servers . . . . . . . . . . . : 202.188.0.133
202.188.1.5
NetBIOS over Tcpip. . . . . . . . : Disabled

Change the NIC on the server as well but still cannot solve the problem

Both of those look fine. If you really still can't ping from the two computers, could you trying disabling the other two connections on the server, and the other connection on the client. In Networking Connections, right-click the connections and select Disable. Leave yourself with just the one internal connection on each computer. Then try pinging again.

i think u need to use a straight through cable instead of a crossover cable...

a few things. if you are connecting from one machine, through a cable, to a NIC in your server, you do need a crossover cable. check the cable, make sure that if you look at the colors in the plugs with the pinch-pin away from you, the colors look like then do in this site http://www.davidj.org/tools/cabler/cabler.html as long as the two ends look like that (not the same pattern) the cable is ok. if you are using a hub, then both plugs should look exactly the same O/W O G/W BL BL/W G BR/W BR by standard convention.