altered_computers

We've got a 2000 Server set up as our DC, and it seems to work ok (no major issues), but the other day I was looking around a saw "Server Options" from the DHCP Administrative Tool. There are a ton of settings to set, but I don't know what the benefit would be of setting them. Things like Time Server (it already gives NT clients the time), Name Server (again, it's working as is), etc. Should I fill in the fields and just use the local machines IP? Thanks for any info

Also, I forgot to add that the DC doesn't run WINS. Just something to add to the mix.

I got Cyberkit, and noticed that when I stop the RRAS service, the 9x clients ping the LAN (x.x.x.2) IP instead of the x.x.x.32 IP they ping when it's running. Is RRAS listening on the wrong adapter? Quote: Does this occur only when you establish a tunnel or immediatley after booting your 9x clients? Well, I was playing with the VPN from a couple of the LAN PCs, not PCs across the internet, so that may have something to do with it. It's never been connected to via an internet machine. But yes, if RRAS is running, as soon as they boot, they ping the wrong address.

Well, part of the reason I ask, is because I just enabled a VPN on our ISA server. After making the change, the machine got a 2nd IP address. Now, all of the 9x clients in our office ping the WAN IP instead of the standard LAN IP. I was wondering if setting one of those DHCP params would alleviate the need to put the ISA server's LAN IP in the hosts file for the legacy clients. As far as I can tell, the NT clients are fine.

Has anybody tried this with RTM Win2k3? I remember that you could change XP Pro to "Whister Server" but it had a bad memory leak. I don't have a copy of 2003 to play with, but I assume anything that NTSwitch changes still works. (?) Would it convert it into basically XP Pro SP2ish? Just wondering if anyone's tried it. Let us know, eh?

This is what I do when I want to clear out the remnents of 6 different nic's in my PC - Granted, I'm no expert, but here's how I do it. Disclaimer: Althought I've never had to reinstall because of it, I don't know or guarentee that this will work on your PC. Maybe it will, maybe it won't. Just PLEASE make a registry backup before starting. Win2k: Open regedt32, and browse to \HKLM\System\CurrentControlSet\Enum Under Enum, there should be a bunch of sub-keys. Depending on whether your PC is ACPI or not, it should have entries named ACPI, ACPI_HAL, DISPLAY, FDC, ROOT, PCI, etc. Go through these, and for my machine, most of the drivers I wanted to clear out were under the PCI key. I identified which key had the device I wanted to clear, then under Security/Permissions, change to full control. Then it allows you to delete the key. I don't know if it makes a difference to delete the individual keys that contain all the info on the device, but I just do what works for me. Oh yeah, it might be a bad idea to delete the key with info on your boot drive's controller. I assume it would give you the STOP - Inaccessable boot device error if you did. I'm not about to try it myself, so I don't know.

My apologies for the long delay. I found the problem that we were having here. It was the Firewall Client installed from the ISA server. I don't yet know what was causing the lack of connectivity, but removing the Firewall Client allows the system to boot totally normal afterwards. But thanks to everyone who took the time to troubleshoot. Much appreciated.

Freddy, glad you got your issue resolved! It's just too bad it's not that simple for me 8) I'm unfamiliar with what IP forwarding is exactly. I'm also unclear whether we should have a default gateway or not. Basically, it's a small office, with one main server (WAS connected to the internet, but now it's a seperate machine) running DNS, DHCP, AD, etc. So any internet (external) requests just get routed through the ISA server machine. :edit: Oh yeah, the main server is also running stuff like Exchange 2000, SQL Server 7, Borland Interbase, ISA Server is still installed, but the services are stopped.

Quote: That's DNS info, right? Is your MAIN box acting as its own DNS server without pointing to another one out there online?? On your first question regarding the DC pointing to itself, if it's acting as its own DNS server it still has to ask for URL to IP resolution SOMEWHERE, at least for outside internet addresses I imagine... ISA server handles that for you though, right? Yes, the DC is running DNS, but only for addresses internal. For web requests, yeah, the requests go through the ISA server. Although I don't know how the DC determines to use the ISA server, because it's not defined anywhere on the server. The clients all have the MS Firewall Client installed & proxy set up in their browsers. Should the default gateway be the IP of the ISA server? If so, internal(NIC) or external(Modems) interface? It seems to me like there's some correlation between this DHCP problem and the NIC Connection Properties dialog hanging when I change IP settings. Doesn't it seem that way?

Here are the results from a few machines. MP3 & Brad_dev have the rebooting problem. ShouckXP is my machine, and ISSI-SERVER2 is the DC. Windows 2000 IP Configuration (Another machine with rebooting problem) Host Name . . . . . . . . . . . . : mp3 Primary DNS Suffix . . . . . . . : issi-domain1.local Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NETGEAR FA311/312 PCI Adapter Physical Address. . . . . . . . . : 00-02-E3-02-AC-49 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 169.254.0.99 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : DHCP Server . . . . . . . . . . . : 169.254.0.1 DNS Servers . . . . . . . . . . . : Lease Obtained. . . . . . . . . . : Tuesday, March 04, 2003 10:05:50 AM Lease Expires . . . . . . . . . . : Wednesday, March 12, 2003 10:05:50 AM _________________________________________________________________________ Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : brad_dev Primary DNS Suffix . . . . . . . : issi-domain1.local Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX NIC(3C905B-TX) Physical Address. . . . . . . . . : 00-50-04-AF-37-97 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 169.254.0.21 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : DHCP Server . . . . . . . . . . . : 169.254.0.1 DNS Servers . . . . . . . . . . . : Lease Obtained. . . . . . . . . . : Monday, March 03, 2003 8:46:38 AM Lease Expires . . . . . . . . . . : Tuesday, March 11, 2003 8:46:38 AM _________________________________________________________________________ Windows IP Configuration (XP Client that does not have problem) *Notice that DNS Server is filled in* Host Name . . . . . . . . . . . . : shouckXP Primary Dns Suffix . . . . . . . : issi-domain1.local Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : issi-domain1.local Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI TX NIC (3C905B-TX) Physical Address. . . . . . . . . : 00-50-04-B0-D7-AB Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 169.254.0.17 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : DHCP Server . . . . . . . . . . . : 169.254.0.1 DNS Servers . . . . . . . . . . . : 169.254.0.1 Lease Obtained. . . . . . . . . . : Tuesday, March 04, 2003 9:35:23 AM Lease Expires . . . . . . . . . . : Wednesday, March 12, 2003 9:35:23 AM _________________________________________________________________________ Windows 2000 IP Configuration (Domain Controller) Host Name . . . . . . . . . . . . : issi-server2 Primary DNS Suffix . . . . . . . : issi-domain1.local Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : issi-domain1.local Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : 3Com EtherLink 10/100 PCI TX NIC (3C905B-TX) Physical Address. . . . . . . . . : 00-50-04-AF-37-68 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 169.254.0.1 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : 169.254.0.1 DNS Servers . . . . . . . . . . . : 169.254.0.1

Yep, the subnet's the same, 255.255.0.0 (I'd rather it be 255.255.255.0 but it was set up like that when I hired in). I did notice that on the DC, it's default gateway is pointed to itself. It's NIC address, not a 127.x.x.x addresss. Is that correct? I've got an ISA server set up, but ISA was running on the DC for a long time. Also, what kind of data & details would you like? I can give you whatever you want/need. And it's a Windows2000 Server SP3 AD domain, no NT4 machines, some 98/Me, and I think the domain is in mixed mode. I would switch to native, but I just don't know what that would do. Client for Microsoft Networks on all the machines, yes. PS: I had a problem with nslookup for a long time, it would say UnKnown Server & Default server unavailable, but I seem to have fixed it a few minutes ago. Just rebooted another 2000 machine, and I got Event 5719 again, so the nslookup problem wasn't it. :edit: Sorry, forgot to mention- we're connected to the internet via 2 56k modems from the ISA server. (Thought it might relate to the default gateway setting)

Here are the logs from the 2000 client that loses the info- I chopped off extra info, I don't know if this is the desired format, but here it is. The first listed event is the first event after the event log startup & Windows 2000 uniprocessor free, etc. I'm checking the server logs now. Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5719 Date: 3/3/2003 Time: 8:12:55 AM User: N/A Computer: BRAD_DEV Description: No Windows NT or Windows 2000 Domain Controller is available for domain ISSI-DOMAIN1. The following error occurred: There are currently no logon servers available to service the logon request. EVENTID.net for that error says to visit these 2 MSKB articles, but they don't help. Q228901 and Q247922. Event Type: Error Event Source: Server Event Category: None Event ID: 2506 Date: 3/3/2003 Time: 8:12:58 AM User: N/A Computer: BRAD_DEV Description: The value named IRPStackSize in the server's Registry key LanmanServer\Parameters was invalid. The value was ignored, and processing continued. I've gotten this error before, and I don't think it hurts anything. I just picked it because it was a few seconds after the first error. Event Type: Warning Event Source: w32time Event Category: None Event ID: 54 Date: 3/3/2003 Time: 8:13:01 AM User: N/A Computer: BRAD_DEV Description: The Windows Time Service was not able to find a Domain Controller. A time and date update was not possible. Obviously, since the NIC interface's config is blank.

Just checked the services, and DHCP & DNS client are both started. I can't check a few of the things, just because I can't kick the user off (our main programmer) during work hours. I looked in the event log and there's quite a few errors, but I don't know which one would be of most interest. Shall I post the errors?

Latest drivers? Depends whether I go with the Windows Update drivers or the latest from the 3Com. I'll look at that. Haven't tried a static IP, but I do have a DHCP reservation for that PC. I'll try that as well. The patch cables are OK, I think, but I know that the cabling in the wall was repaired a couple years ago. I'll try different cables. An ipconfig /renew just hangs. As does changing any properties of the IP configuration dialog. I figured that the IP stack was damaged, so I removed it, rebooted, reinstalled it, and it picked up the ip address, but when you reboot, it's gone, or before rebooting, if you change properties of the IP config, it hangs. Strange eh? But thanks for the tips, greatly appreciated. :edit: I checked the registry as per the Windows2000faq link, and it's not dependent on the symantec service. It was dependent on: Tcpip Afd NetBT

First post, hey everyone- I've been having the same problem here. DHCP & DNS on the PDC, one Win2k client, every reboot, has 0.0.0.0 (no IP config). It's not pulling from the DHCP server. That's IF the NIC cable is connected. If I reboot with the ethernet cord disconnected, login, plug in, all the correct info is there. It seems to have a problem only if it's connected when the NIC is initialized. BTW, it's a 3Com 905B on both server and client. But sorry I don't have a solution to your XP problem.