Ok, things are moving along slowly but surely.

Apparently, DHCP works as I can in fact reach the net through my company's LAN. The problem is, regardless of browser, it has a long "warmup time" where firefox/konqueror will say "resolving host" or something like that, for a good 5 or 6 seconds. After that, the T3 seems to kick in and the page loads instantly. Dual-Booting into Windows on the same LAN and using firefox .8, there's no delay, so I'm sure its a Linux issue.

Also, I cannot get Ethereal to reconize my eth0. When I try to select an adapter, there are none listed. Could this be part of the issue? Likewise, I cannot start Nessus on localhost, as it tells me it cannot reach the port (which should not be blocked). Could these be related?

Should there be a specific DHCP or other package I should install? It seems to reconize my Realtek Gigabit LAN adapter during boot.

This "lag" won't do for network scanning! Thanks for your help again!

You are running kernel 2.6, right? Concerning the "resolving host" problem, there has been a looong thread in the Linux-Networking forum.

The bottom line is, that disabling IPv6 support in the kernel seems to fix it (in some/most cases), although this might be overkill. Another solution, that worked for some, was to add to /etc/modprobe.conf. It still isn't clear to me what causes this behaviour in the first place.

Oh, I thought this was just some noob config issue

What exactly does that code do? Will it effect anything else?

As far as I can tell, net-pf-10 is the name of the module that handles IPv6, and is being swtiched off by that command. I don't know if this module is responsible for other stuff as well.

Oh, and I believe you would need to do an "update-modules" after editing /etc/modprobe.conf.