Ok. I'll find out what's going on. I did do a remove of the nic and
tcp/ip, but after I do that, TCP/IP is no longer available in the vnet
config. So, I ended up having to reinstall a personal install yet again.
I'll try your steps and see what happens. Doesn it matter that I have
Filters or IPv6 compiled in my kernel as well? Filters aren't used, I just
have them in there for possible use later.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED]
On Thu, 31 May 2001, Mike Badger wrote:
> Ok, There has been some good information posted by Austin and Brandon. Give me
> some time to sort it out and let's see what we can come up with.
>
> Austin, if you can not ping 127.0.0.1 you'll never get anywhere. In Windows
> remove / add
> tcp/ip from the Network control panel, then try pinging 127.0.0.1 again.
> When I remove a component
> such as tcp/ip from windows, I typically don't reboot between removing
> tcp/ip and adding it back
> in. I do reboot after I put it back in. That's my preference for what it's
> worth.
>
> The tmp key makes no difference here.
>
> Mike
>
> At 12:19 AM 5/31/01 -0500, you 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?
> >
> >--
> >Austin Gonyou
> >Systems Architect, CCNA
> >Coremetrics, Inc.
> >Phone: 512-796-9023
> >email: [EMAIL PROTECTED]
> >
> >On Wed, 30 May 2001, Darb wrote:
> >
> > > Yeah, vnetd-2.4 started automaticly. Static IP configuration did
> > > work... So did setting up a dhcp server on the local machine. I can
> > > tell you though, my company won't want me running my on dhcp server on
> > > the same subnet they already serve with dhcp. Something is wrong with
> > > vnetd recognizing dhcp offers from servers on different subnets... yet
> > > it sares the same router.
> > >
> > > *Brandon
> > >
> > > Austin Gonyou wrote:
> > >
> > > > I'm having the same problem. I tried even assigning an IP though and that
> > > > didn't work either. At first, I thought it might be my install, so I
> > > > cleaned the system totally, then re-installed win4lin and windows. No
> > > > dice. Here is a question. When windows starts up does it startup a
> > > > vnetd-2.x automatically? or is there something else which happens here?
> > > >
> > >
> > >
> > > _______________________________________________
> > > 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
>
> _______________________________________________
> 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
