• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

multihomed networking help!

R

r6ashih

Senior member
okay I want to add a win2k server machine to our domain network to run a database so that it can be accessed from outside.

It has 2 network cards, one of them is getting dhcp from the domain controller with the dns pointing to the dc. the other is a static ip from the ISP with the dns pointing to the isp's.

Is everything correct so far?

I'm getting this error in the system event viewer:

The IP address lease 192.168.0.71 for the Network Card with network address 000C41EED2A8 has been denied by the DHCP server 67.*.79.9* (The DHCP Server sent a DHCPNACK message).

and this warning:
The system failed to register network adapter with settings:

Adapter Name : {A9AD9278-8FD7-4483-A031-05B24BC44723}
Host Name : alex2
Adapter-specific Domain Suffix : alexsd
DNS server list :
192.168.0.1
Sent update to server : None
IP Address(es) :
67.9*.*9.99

The cause of this DNS registration failure was because of DNS server failure. This may be due to a zone transfer that has locked the DNS server for the applicable zone that your computer needs to register itself with.

(The applicable zone should typically correspond to the Adapter-specific Domain Suffix that was indicated above.) You can manually retry registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions.

another warning:
The server was unable to logon the Windows NT account 'test' due to the following error: Logon failure: unknown user name or bad password. The data is the error code.
For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.

thanks
 
Originally posted by: r6ashih
okay I want to add a win2k server machine to our domain network to run a database so that it can be accessed from outside.

It has 2 network cards, one of them is getting dhcp from the domain controller with the dns pointing to the dc. the other is a static ip from the ISP with the dns pointing to the isp's.

Is everything correct so far?
Click to expand...

Why are you setting it up this way? Why not set a static IP internal w/ port forwarding from your firewall?

I'm getting this error in the system event viewer:

The IP address lease 192.168.0.71 for the Network Card with network address 000C41EED2A8 has been denied by the DHCP server 67.*.79.9* (The DHCP Server sent a DHCPNACK message).

and this warning:
The system failed to register network adapter with settings:

Adapter Name : {A9AD9278-8FD7-4483-A031-05B24BC44723}
Host Name : alex2
Adapter-specific Domain Suffix : alexsd
DNS server list :
192.168.0.1
Sent update to server : None
IP Address(es) :
67.9*.*9.99

The cause of this DNS registration failure was because of DNS server failure. This may be due to a zone transfer that has locked the DNS server for the applicable zone that your computer needs to register itself with.

(The applicable zone should typically correspond to the Adapter-specific Domain Suffix that was indicated above.) You can manually retry registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions.

another warning:
The server was unable to logon the Windows NT account 'test' due to the following error: Logon failure: unknown user name or bad password. The data is the error code.
For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.

thanks
Click to expand...

What is your actual ip for the internal interface? From command promp type ipconfig /all and it will be in there.

It looks to me like you're not getting a proper registration In DNS (internal DNS) because your Internal NIC is not registeded in DHCP and does not have a valid private IP address. Never the less the internal NIC is still trying to register IN DNS with the incorrect IP. 67.9*.*9.99.

You need to find out why DHCP is rejecting you and fix that problem because you need to get a good internal IP. Check your TCPIP settings then Internal network cable etc... You might benefit from disableing the external interface temporarily and focusing on the internal. HTH.
 
we dont have a firewall, all we have are a switch and a domain controller acting as a dhcp server.

Actual ip for the internal interface? its getting the ip address from the dhcp server(the domain controller )

typing ipconfig shows like it is getting everything alright. Do you think that maybe it is using the WAN card as the primary card, thus using the wan ip to try to access the dhcp server?

Maybe setting the metric lower on the LAN card will solve it?
 
You can set the interface order in Windows 2000 Set the internal interface as priority. I forget exactly how to get there (to Explain it). Maybe someone could chime in.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top