is DHCP required when using two NIC's?

[hawat.thufir]

follow up to microsoft.public.win2000.networking, please


I'm looking at "DHCP (Dynamic Host Configuration Protocol) Basics,"
in relation to a k7som+ mother board, a NIC, and an a 802.11g wi-fi
network adapter.

Because there are now two ethernet jacks for this computer, which I've
named Arrakis, is DHCP required to configure the wireless network
adapter?

the asus utility isn't even recognizing when the wireless network
adapter, a wl-330g, is plugged into the mother board's ethernet NIC.
the utility is recognizing when the wl-330g is plugged into the new,
secondary, NIC but IE isn't able to access the internet.

I know that the wl-330g works because I'm using it right now, on a diff
computer
the computer in question was working fine *before* installing the new
NIC.


links:
<http://support.microsoft.com/default.aspx?scid=kb;en-us;169289>
<http://www.ecsusa.com/downloads/manual_k7s.html>
<http://usa.asus.com/prog/spec.asp?m=WL-330g&langs=09>
<http://www.dlink.ca/product.php?PID=124>


thanks,

Thufir

ps:

as usual, when I submitted this as a technical inquiry on asus I
received window with the following error message:

[JavaScript Application]
Server Connection Failure!
Please try again later.


I took the wl-330g back to where I purchased this, apparently this has
now been going on for about a week, it's not just on my end.

 

[Pegasus \(MVP\)]

DHCP is ***never*** required - it is merely a tool of
convenience to assign IP addresses automatically.
DHCP works most of the time it works but sometimes
it does not.

I suggest that you set all your addresses (IP address,
default gateway, DNS) manually during the testing
phase. Setting up a wireless can be difficult enough -
no need to do battle with a DHCP server that may
or may not work.

 

[j9]

YOu can set them with static addresses, or you can set either/both of them
with an external DHCP source. It really depends what you want to do with
them....

 

[Tony]

If you have a small number of clients, static ip's might be ok. But if
you've got numerous client connections that require ip assignments, save
yourself sum headache and setup a DHCP server. There's no evidence that DHCP
is any less reliable on wireless connections. Just follow the rules when
setting up Wireless Access Points and you'll be fine. (The verdict is still
out by the way whether wireless security protocols are suitable for mission
critical scenarios.)