Windows 2000 server network

Hi,


I installed windows 2000 server in my office computer.
Iam using 2 ethernet cards on server to controll network traffic.
and i configured domain controller on server, its working fine.
ETH0 IP= 100.100.100.1
ETH1 IP= 100.100.100.2
Hosts IP's = 100.100.100.x

On eth0 20 hosts(win9x) is connected and all are working properly (with domain controller).
If iam trying to connect other computers on ETH1 iam not getting domain controller only.
while logging windows(hosts) error is comming "No Domain Controller is avilable to walid your user name or Password"
but iam  getting reply on ping command (100.100.100.2) from hosts computers.


What could be the problem. Please help me.
Hussain
hussain_netAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

qwaleteeCommented:
This setup does NOT make sense.  If you havetwo different NICs, they need to be on two different subnets. Otherwise, the server might be able to receive traffic on both, but would always send traffic on one. Not sure how ping would have worked.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mikeleebrlaCommented:
qwaletee is correct in stating that each NIC needs to have its own subnet, but he/she didn't elaberate on how to do this. Set up one with 192.168.1.x and a subnet mask of 255.255.255.0 and the other with 192.168.2.x and a subnet mask of 255.255.255.0.  This will give you 2 seperate subnets in a private range, not one big subnet of 100.x.x.x which is in a public range anyway and could cause you DNS problems down the line.

Thanks  
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.