On Wednesday 16 January 2002 17:14, Alex McLintock wrote: > > Good, you can open a "run..." dialog box and enter "winipcfg", > > select your Nic in the adapter box, and push the "more info" button > > to get info on your Gateway and dns server ip addresses.
We'll see if we can slip it in somewhere. > Aha! Thanks for that. Please put it in the FAQ :-) > It told me that my IP address for the laptop was 80.1.127.3, > Gateway 80.1.127.1, > DNS 194.168.4.100 > DHCP server 10.0.122.70 This is a good, routable ip that should be good. Maybe releasing it in Win98 before switching to Dachstein would fix the problem. > Now when I boot up my DachStein box (just after the cable modem set > top box!!!) it gets the same DHCP server. I get a line something like > DHCPREQUEST on eth0 to 10.0.122.70 port 67 > DHCPACK from 10.0.122.70 > eth0 bound to 10.50.14.4 This is a non-routable private class ip..... this should _not_ be a good ip address. Maybe a call to your ISP would resolve this, some ISP's map to MAC addresses on the connected NIC causing strange errors like this. But the DENY's below seem to indicate that the DHCP server is trying to send more info, but that it is blocked by the firewall. I would think that this might well be the problem. > Packet log: input DENY eth0 PROTO=1 10.50.14.4:8 10.50.14.0:0 L=84 > S=0x00 I=126 F=0x0000 T=64 (#17) > Packet log: input DENY eth0 PROTO=1 10.50.14.4:8 10.50.14.0:0 L=84 > S=0x00 I=127 F=0x0000 T=64 (#17) > Packet log: input DENY eth0 PROTO=1 10.50.14.4:8 10.50.14.0:0 L=84 > S=0x00 I=128 F=0x0000 T=64 (#17) > Packet log: input DENY eth0 PROTO=1 10.50.14.4:8 10.50.14.255:0 L=84 > S=0x00 I=129 F=0x0000 T=64 (#17) > Packet log: input DENY eth0 PROTO=1 10.50.14.4:8 10.50.14.255:0 L=84 > S=0x00 I=130 F=0x0000 T=64 (#17) > > Packet log: input DENY eth0 PROTO=17 172.16.30.83:53 10.50.14.4:1024 > L=116 S=0x00 I=1365 F=0x4000 T=246 (#8) > Packet log: input DENY eth0 PROTO=17 172.16.30.84:53 10.50.14.4:1024 > L=116 S=0x00 I=15785 F=0x4000 T=244 (#8) > Packet log: input DENY eth0 PROTO=17 172.16.30.83:53 10.50.14.4:1024 > L=116 S=0x00 I=1366 F=0x4000 T=246 (#8) > Packet log: input DENY eth0 PROTO=17 172.16.30.84:53 10.50.14.4:1024 > L=116 S=0x00 I=15786 F=0x4000 T=244 (#8) > Packet log: input DENY eth0 PROTO=17 172.16.30.83:53 10.50.14.4:1024 > L=116 S=0x00 I=1367 F=0x4000 T=246 (#8) > Packet log: input DENY eth0 PROTO=17 172.16.30.84:53 10.50.14.4:1024 > L=116 S=0x00 I=15787 F=0x4000 T=244 (#8) This 172.16.x.x. is another private class block, it appears to be a DNS server returning a request from your firewall/network. All in all, your ISP is doing unusual things with trying to run their service(s) servers on RFC private class ip's. You can open these private blocks in the firewall and I would assume things would work, but I would be _very_ unhappy about it..... other private networks on the same public block that don't seem to contain their private traffic could cause problems with yours if these blocks are open. -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! ------------------------------------------------------- -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
