I found out what the issue is I believe. In both locations, work and Home,
I had IPv6 compiled into my kernel. At home, in a last ditch effort, I
disabled the following:
ip multicasting
ipv6 support
memory mapped IO
After that, I simply just rebooted my box to the new kernel, restarted
win4lin, and voila, I actually got a DHCP lease this time. I tried pinging
my own IP, good. Then my immediate gateway, good. Then www.dell.com. Good.
All's well in pingsville. :) I then tried windows update. Bam, no problem.
All's well here. One thing I did prior to any of this also to make sure
I've got no MAC issues was set the MAC manually so it's static, based on
the last 4 of my own NICs mac.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED]
On Thu, 31 May 2001, Brian Keegan wrote:
> Austin
>
> Can I see the output of "ifconfig -a" for your system? This might help me to
> offer an explanation. Send it to me directly if you are security conscious and
> down want to broadcast your internet metrics to the group.
>
> Thanks,
>
> Brian
>
> Austin Gonyou wrote:
>
> > Here's an odd thing I calculate that my ethernet address should be
> > 18:18:18:3e:44:00 per Brian Keegan's last email. But my addy is now this,
> > after a full reinstall of win4lin, and a new personal
> > windows install. 18:18:FF:FE:00:01
>
>
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
