GA-7VM400M rev 2, no DHCP for onboard NIC

Are you sure there is ONLY ONE DHCP server on the network?

Quite

-GV

Is there anything useful in the XP Event Log?

Didn't check. Will do so next time the customer's machine is here,
but I doubt there will be anything useful.

-GV

Travis thanks for the ideas, but I think I've now narrowed down what's
really going on. I installed an ATI card in a machine tonight (not a
gigabyte board) and the network completely stopped working (even with
a static IP...). I was able on this board to disable the "assign IRQ
for VGA" and poof, the network magically worked again. I think the
problem lies in the ATI not sharing it's IRQ more so than it being a
problem with the board, however if I remember correctly there was no
option to turn off the IRQ for VGA on this gigabyte board (which
really sucks!). Anyway I should have that customer's machine back
tomorrow to work on, if there is an option to turn the VGA/IRQ off
I'll do so and I'll bet that solves the DHCP problem. It really
sucks, as ATI makes pretty nice cards.

-GV

i have the onboard lan problem too me thinks its service pack 2. How i
solved this problem using a static ip is disable the dhcp service on
both host and client machines, In control panel\admistrative
tools\services in the services (local) tree you will see dhcp client,
double click that and then change the automatic setting to disbled.
when setting the tcp gateway on the client machines right click on my
network places select properties, right click on local network
conection select properties double click on internet protocol tcp\ip,
you will see (use the following ip address) check that & type in
192.168.?.? the q mark equals any number between 1 and 255 (you can
use 0 on the first parameter ? but not on the second). set default
gateway to 192.168.0.1 ... now here is the important part preferred
dns put your default gateway address 192.168.0.1 ... reboot all the
machines logon and make sure you allow the client firewalls to allow
192.168.0.1 and the host to allow your new client ip address you
assigned i have found this to be stable and very secure as your host
is not broadcasting ip address's to any machine that tries to log on
and you dont have to allow an ip field on your host's firewall ie:
192.169.0.1-192.168.255.255 this confines your network to allow only
the ip's you define in your firewall and solves the problem of the
dhcp assigning your ics host bogus ip address's to your clients "its
rock stable"

I don't have an ICS machine giving out IP's. Besides, I already
posted the problem is that the ATI video card doesn't share it's IRQ,
and there's no way to disable "assign IRQ for VGA" in the BIOS of this
board (boo, gigabyte!). If I could do that, or if I had another video
card (ie NVidia) I'm sure DHCP would work fine.

i have the onboard lan problem too me thinks its service pack 2. How i
solved this problem using a static ip is disable the dhcp service on
both host and client machines, In control panel\admistrative
tools\services in the services (local) tree you will see dhcp client,
double click that and then change the automatic setting to disbled.
when setting the tcp gateway on the client machines right click on my
network places select properties, right click on local network
conection select properties double click on internet protocol tcp\ip,
you will see (use the following ip address) check that & type in
192.168.?.? the q mark equals any number between 1 and 255 (you can
use 0 on the first parameter ? but not on the second). set default
gateway to 192.168.0.1 ... now here is the important part preferred
dns put your default gateway address 192.168.0.1 ... reboot all the
machines logon and make sure you allow the client firewalls to allow
192.168.0.1 and the host to allow your new client ip address you
assigned i have found this to be stable and very secure as your host
is not broadcasting ip address's to any machine that tries to log on
and you dont have to allow an ip field on your host's firewall ie:
192.169.0.1-192.168.255.255 this confines your network to allow only
the ip's you define in your firewall and solves the problem of the
dhcp assigning your ics host bogus ip address's to your clients "its
rock stable"

-GV

its become clear to me this network is not an ics network and the
customers connect through a router. research has shown me the dhcp
service is security for customers at the expense of server security
Ie: to allow ease of automated connections & giving a new ip to
the clients when the client logs on so hackers cant harrass clients
on the same static ip ... hmm ,Its not clear to me what sought of
service you are running: isp ect so the advantages of running dhcp
cant be acertained. do you connect out to a different sevice ect
there are a lot more complications to the problem here other than
interupt requests. Please give more details

its become clear to me this network is not an ics network and the
customers connect through a router. research has shown me the dhcp
service is security for customers at the expense of server security
Ie: to allow ease of automated connections & giving a new ip to
the clients when the client logs on so hackers cant harrass clients
on the same static ip ... hmm ,Its not clear to me what sought of
service you are running: isp ect so the advantages of running dhcp
cant be acertained. do you connect out to a different sevice ect
there are a lot more complications to the problem here other than
interupt requests. Please give more details

None of that matters. The DHCP was for ease of use, the customer is
not technically minded. Again, it is/was a hardware conflict with the
ATI video card, which there is no way to resolve other than changing
to an NVidia card, as there's no option to disable "Assign IRQ to VGA"
on this board, as there IS on SO many other boards out there (why,
Gigabyte, why??). Anyway, a static IP works fine for their use and I
consider that case closed until the board or video card are changed.

-GV