On Thu, 31 May 2001, Austin Gonyou wrote:
> I got tcpdump info. Here it is:
> 00:15:44.545091 eth0 P 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0x1e77e51b [|bootp]
> 00:15:48.554218 eth0 P 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0x1e77e51b secs:18822 [|bootp]
> 00:15:55.564209 eth0 P 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0x1e77e51b secs:18822 [|bootp]
> 00:16:11.604209 eth0 P 0.0.0.0.bootpc > 255.255.255.255.bootps:
> xid:0x1e77e51b secs:18822 [|bootp]
>
> As you can see, requests are made, but no replies. This was ALL I got.
> I'll attempt this at work and see what happens. For now, it's pretty much
> useless. It can't even ping itself if I assign an IP to it! I can't even
> ping 127.0.0.1. I get request timed out. HEEEEELLLLLPP. Btw, does it
> matter if I have a temp key or not?
Let me know how it goes. This is kind of mystifying. I have a gnatbox
firewall, running DHCP server. My win4lin session (just installed),
grabs an IP fine. Odd...
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
