I have a Win2K Pro machine connected to a Win2K Server. I was playing with the server a bit, and now it seems I have to go through the following procedure to connect to the server:
- Disable the client network connection
- Disable the server network connection
- Enable the server network connection
- Enable the client network connection
Both network cards are 3com 3c905s with the same driver being used on both machines. The server has one static IP NIC (169.254.0.1) and 2 other NICs installed. DHCP is supplying those with dynamic addresses. The client address is dynamice as well (I've tried statics with no effect). The two settings are as follows:
Client
IP 169.254.0.xx (dynamic)
Subnet Mask 255.255.0.0
DNS Server 169.254.0.1
Server
IP 169.254.0.1
Subnet Mask 255.255.0.0
DNS Server 169.254.0.1
I can start the server, wait 15 minutes, then start the client with the same symptom. The only other interesting symptom is that ROTE PRINT on the server shows two 169.254.0.0 entries pointing to two different gateways... one the static IP NIC, and another one of the dynamic IPS (which by the way DHCP shows in its server title...why I don't know... not a DHCP expert here).
NO DNS or DHCP errors in the event log.
Help me to not have to perform that procedure of disable/enable on the client and server please!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
hmm
Try to configure both Dynamic cards in the server with Static IP Addresses, then look in the DNS Settings in the DHCP scope if this is targit correct addresses. then
kill DHCP Services in services task restart services.
It seems generally that you might have encountered a DNS problems. Cause in Win2000 DHCP is also using the DNS to provide Zones in DNS...
Well, changing to 192.168.5.x seemed to require demoting and promoting the Domain Controller.
Now DHCP and DNS seem to be set up OK to my eyes, but the client cannot get an IP address from the server.
The Active Directory and DNS both say the client has leased 192.168.5.70 (first in the dynamic range), but the client 3c905 NIC has a 169.254.x.x address and ipconfig /release says it doesn't have a DHCP address.
I can't ping 192.168.5.1, which is the server 3c905 NIC.
The other two server NICs have 192.168.5.2 and 192.168.5.3 now (static).
It also takes the client a long time to get past the network connections startup screen, or to ipconfig /renew.
Help!
The cable is fine too. The trouble was the combination of trying to set up a VPN on a domain controller. Once RRAS was disabled, client connectivity worked fine again.
The following webcast mentions how difficult it is to set up a VPN on a domain controller. I've has this problem before too, I just forgot that RRAS was the culprit.
http://support.microsoft.c
RadRichie:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
Business Accounts
Answer for Membership
by: Flash828Posted on 2003-03-09 at 20:02:43ID: 8100503
It doesn't sound like DHCP requests are going through. Those look like default values for when windows fails to recieve a DHCP ACK response. Check to make sure your dhcp services are running properly. See if you can switch your network to the private class C range, which is 192.168.x.y where x is a user-specified network number, and y are the host numbers (where 0 < x,y < 255). Your DHCP server should be providing 192.168's to everyone.