streeter

Sort of agree with you - for instance the internet connection sharing wizard sets up a nameserver, proxy server and a dhcp server - on a simple home network, these are not really needed - too much complication. But having said that, I installed a fresh copy of mdk 10 yesterday with no firewall or servers and it all worked perfectly, first time. Even with the wizards. Didn't have to enter any more networking information or do anything more than you do when installing windows. If you are still with us, post the output of "iptables -nvL" and "iptables -nvL -t nat" , "route -n" and "ifconfig eth0" and we will see what we can do. Or if you haven't set up too many other things yet, reinstall, but don't set up networking yet - then we know it is clean. Chris

OK - your network interfaces are all working (eth0 is being assigned automatically using dhcp by the router - thats OK) - we now need to allow packet forwarding on the Linux box. DO NOT run the mandrake internet connection sharing wizard - it may break things. First, install iptables - type "urpmi iptables" . It may already be installed, if so then that's OK. Then post the output of "iptables -nvL" and "iptables -nvL -t nat" here. Chris

OK - don't touch anything else yet... Can you ping 10.0.0.2 (the modem)? Please post output of "iptables -nvL" What error message do you get in the browser? Chris

>>[root@dualbooter andrew]# ipconfig That should be ifconfig - second letter is an F. Please post again. You don't have anything in your routing table, so I suspect your network card is not up. ifconfig will tell us that. First thing to do is copy down all the network settings from the windows config - IP address, netmask, default gateway. As these work, they should be used on the Linux box. The file you need to edit is /etc/sysconfig/network-scripts/ifcfg-eth0 - the entries should read : DEVICE=eth0 BOOTPROTO=static IPADDR=192.168.0.20 # may be different on your PC NETMASK=255.255.255.0 # may be different on your PC NETWORK=192.168.0.0 # may be different on your PC BROADCAST=192.168.0.255 # may be different on your PC ONBOOT=yes MII_NOT_SUPPORTED=yes /etc/resolv.conf should have valid nameserver addresses - are you really running a nameserver on your network? If not, put the address of your ISPs nameserver (get it from windows) at the top. The default gateway goes in /etc/sysconfig/network: HOSTNAME=yourhostname_goes_here NETWORKING=yes GATEWAY=192.168.0.1 # may be different Then type ifup eth0 Reboot if that doesn't work, try again and report back. Chris

Right - I have just used the Mandrake wizards on my laptop, so I now know a little more about them... I have always set things up by hand before, as I don't trust the wizards :) The internet connection sharing wizard sets up a dhcp server, squid and a caching nameserver. You don't always need these - on a home network these servers are just an added complication and more opportunity for things to go wrong.... And if squid (a proxy server) is not set up correctly, you get exactly the results you are getting - the firewall redirects all http requests to squid. So my last post should be right - either try setting up squid again, or set things up manually. Chris

??? Please post output of the command "ifconfig eth0" and your ifcfg-eth0 file again. "Connection to 10.0.0.2 was refused" implies packet filtering - a firewall.. So please install iptables - type "urpmi iptables" as root, then post the output of iptables -nvL -t nat Chris

Back again :) So, do you need to use squid? I suspect not, but if so, you will need to configure it. Try the wizard, but they can be dodgy at times, and you seem to get a very long iptables list... select allow access to the local network. If this doesn't work, try webmin, or ask here - I have it working OK here. If not, remove it with the package manager (preferred option). You should then remove the jump to the entry relating to the proxy from the PREROUTING table. Chain PREROUTING (policy ACCEPT 76 packets, 9875 bytes) pkts bytes target prot opt in out source destination 64 7659 loc_dnat all -- eth0 * 0.0.0.0/0 0.0.0.0/0 This entry jumps to the entry in my last post if any packet comes in on eth0, then the loc_dnat table will match http packets (destination port 80) - which is most requests from your laptop browsers!! It is possible that the proxy server wizard (found in mcc->server wizards->configure proxy) does this for you - anybody know about this? You can remove the entry manually with (should work...): iptables -t nat -D PREROUTING -i eth0 -j loc_dnat Check with "iptables -nvL -t nat" and compare to the output of your last post. If you needed to use the manual command, and your browsers now work, you could put the command at the end of /etc/rc.d/rc.local Chris

Quick reply - got to go out - sorry! 1) eth1 doesn't have an Ip address assigned 2) >>Chain loc_dnat (1 references) >>pkts bytes target prot opt in out source destination >> 4 240 REDIRECT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 redir ports 3128 port 3128 is the squid proxy port - any http request getting to this rule will get redirected to squid - if it's no working.... Chris

Excellent - except for the BOOTPROTO=10.0.0.3 bit - should be BOOTPROTO=static (but that's not causing your problem). So your network is up, and you can ping between the modem and the computer. :) Now we need to look at why you cannot access the modem set up in your browser... Try the browser for me again - type or copy/paste http://10.0.0.2/ exactly like that in the address bar. Then hit the refresh button to make sure. Could also try typing "lynx 10.0.0.2" in a terminal - this is a text based browser, and may work for you. If neither of these work, there is a reset button under your modem (see your manual) Press it and try again. Chris

You have still got the IP address of your PC set to 10.0.0.2 ! So you are pinging the PC eth0 network interface... The default IP address of the modem is 10.0.0.2 , so you ABSOLUTELY CANNOT have the same address on your PC. So change the PC eth0 address to 10.0.0.3 in /etc/sysconfig/network-scripts/ifcfg-eth0 and reboot or "ifup eth0" and "ping 10.0.0.2" (the modem) should then work, as well as http://10.0.0.2 in your browser. Chris

Have you tried connecting using "telnet your_server 25" - you may get a clue from your servers response. Did RPM save your old config and install a new version, or the other way around (main.cfg.rpmnew) ? if you see what I mean.... Perhaps look at your firewall too? Chris

Couple of things here - set the nameserver to the same nameserver that windows uses- I don't suppose you have a nameserver running on windows. You can find it in network properties. You don't have a default route - set to the IP address of the windows machine - 192.168.0.1. Neither of these will stop you pinging windows though... So: Unless I am missing something obvious... The only similar factor I can see in these two threads, is that neither of you have iptables running. Now, I have never installed Linux without some sort of firewall, so don't know if this makes a difference. Try installing iptables (urpmi iptables), don't set anything up yet, reboot and see if it all starts working... In the mean time, I will install mdk on a spare partition with this config, and see if it makes any difference - never stop learning, do we? :) Chris

First, have you tried another browser? I suspect this could be a proxy problem, so check the settings in Mozilla. Also look at the settings in Mozilla on your desktop - copy them to a laptop. Best work on only one laptop for now. Then, if no proxy is specified in mozilla, have you got a proxy server running on your desktop (eg, squid)? Then, please post output of "iptables -nvL" and "iptables -nvL -t nat" - it is possible all http traffic is being directed to a (non running, or incorrectly set up) proxy by your firewall - I've seen this once or twice. DONT alter any network settings - if you can ftp and ping, basic networking is OK. Chris

You have the same IP address as the modem - this cannot work & BOOTPROTO=dhcp in the file /etc/sysconfig/network-scripts/ifcfg-eth0 -although the modem is supposed to have a dhcp server running as default, we are trying to go static, so change to BOOTPROTO=static and IPADDR=10.0.0.3 . Also change MII_NOT_SUPPORTED=yes. And try again :) Chris PS if you need to send ifconfig output again, you can use "ifconfig eth0" - it's shorter.

OK - just found the (German) manual on line - you need to set your PC IP address to 10.0.0.3 and then access the modem at 10.0.0.2 : Sie sollten den PC wie folgt einstellen, um den Web-Browser benutzen zu können. LAM200E hat die Standard-IP-Adresse 10.0.0.2 , und der DHCP-Server ist aktiv. Siekönnen die IP-Adresse Ihres PC auf 10.0.0.3 oder Auto IP setting setzen. Starten Sie nun den Web-Browser (Internet Explorer oder Netscape). Wenn Sie die Modemadresse (http://10.0.0.2) in die Adresszeile des Web-Browsers eingeben, erscheint das Authentifikations-Fenster. Geben Sie den Benutzernamen und das Paßwort ein. (Standardmäßig lautet der Benutzername admin und das Paßwort epicrouter ). Danach wird das folgende Fenster eingeblendet. Sie können nun das Modem mit Bezug auf Kapitel 4 einstellen. (I don't speak German, but Google does...) :) Chris

Don't know - Need to look at the manual - don't suppose I can download it off the net can I? Or perhaps you could type in the relevent parts? Chris BTW - I don't have ADSL, so just going on general networking concepts here...

Ok - now can you access the router ? Chris

Most ISPs don't like you relaying mail through their servers - after all you might be a spammer for all they know... This means they will only accept mail for the domain they are part of, not anybody elses. Have you set a relayhost=your_isp_mail_server in /etc/postfix/main.cf? I mainly use webmin to configure postfix. You will probably need to enable cyrus-sasl authentication to the relayhost so that they know you are who you say you are - see: http://postfix.state-of-mind.de/patrick.koetter/smtpauth/ I got it working for me, but I remember it being a bit of a struggle... Chris

Okay, I installed RedHat Er, we're Mandrake... :) Anybody here know RedHat tools?

>>I tried manually setting it up and everything. Except what works :) Please see other "my network doesn't" threads here for the information we need from you - ifconfig output and more info on the physical network setup for example. You probably only need to set the default gateway on the linux box to the IP address of the router, but we cannot be sure without more info... Chris

You need the samba package - type urpmi samba as root. Samba is the Linux implementation of the windows smb protocol. When installed, (if it isn't already) it can be configured from webmin (urpmi webmin if not installed) or swat (part of samba). Both are web interfaces. Chris

The IP address (inet Adresse in output from ifconfig command) on Mandrake is 1.1.1.1 - needs to be 10.0.0.2. Change the line in the file /etc/sysconfig/network-scripts/ifcfg-eth0 to IPADDR=10.0.0.2 Save and reboot Type ifconfig to confirm Try 10.0.0.1 in your browser again Let us know how you get on. Chris

Right - we are getting close now... Please follow carefully and post results - What you need to do now is to edit (as root) the file /etc/sysconfig/network-scripts/ifcfg-eth0. Change the IPADDR line to IPADDR=192.168.1.104 and save it. Then in /etc/sysconfig/network-scripts/ifcfg-eth1 do the same, but with IPADDR=192.168.2.1 , the line NETWORK=192.168.2.0 and BROADCAST=192.168.2.255 . This will save the settings across a reboot. In the windows network dialogue, the IP address should be 192.168.2.2 and the default gateway should be 192.168.2.1 . You shouldn't need to change anything in explorer - uncheck the Connections->Lan settings->use a proxy server box. Please don't change anything else for now - one step at a time, or this will get difficult for us... Reboot, and do an "ifconfig" to make sure the IP addresses are correct (eth0 192.168.1.104 & eth1 192.168.2.1). Windows should now be 192.168.2.2, and you should be able to "ping 192.168.2.2" and "ping 192.168.2.1" from windows. The next step is to allow Linux to forward packets for the windows box. Try a "ping 192.168.1.104" from windows - any good? If it works, try "ping 192.168.1.1" from windows. If this works, so probably will your internet connection. If not, as will probably happen, let us know, and we can go on to the next step. Chris

If you still have MDK installed :) , post same info as requested from nawialkair... Chris

Installing another distro is a bit drastic... Some of MDKs wizards are a bit dodgy, but it looks like the network device IS actually set up OK in this case, and the underlying network stuff is standard Linux, which as we know is GREAT for networking :) So - let's recap: Both your network cards appear to work (because you can ping them from the same PC) We think your cables are OK (because they worked before). Still think you should try a crossover cable though - we need to be 100% certain they and your switch are OK. Assume you have unplugged and restarted the switch again. Are they pre-made flexible (as opposed to solid core)cables? Also are all the same coloured wires going to the same pin at both ends? Are all the correct lights on the hubs and network cards on? Do the activity lights flash when you try pinging? We need to make absolutely sure there is not a firewall blocking communication - remember this could be on the windows machine. On windows (XP), right click on the network places icon and choose properties. Right click on the local area connection icon - choose properties again. Select the advanced tab and make sure the internet connection firewall box is unchecked for now. You may also have a 3rd party firewall on windows - if so, disable it for now. On Linux, log in as root and try the "iptables -nvL" for me again, just to make 100% sure. Then try pinging again & let us know. If this doesn't work, let us know what cards you have installed on both machines - on-board, PCI or ISA. Make and model, and are they dual output - ie have they sockets for coax or AUI as well as RJ45 plugs like you are using now. Also, (clutches at straws) not something silly like having 2 network cards in the same machine, and plugging in to the wrong one... (I know, but I've done this myself...) Is there another PC/dual boot with windows you can use to test the connection or cables - mate got one? (laptop easiest...). Or even a knoppix CD. Then we may be able to rule out one of the PCs. Please also post output of ifconfig again - I see there are Rx errors - which implies there may be something getting through... Running out of ideas if the above doesn't help, but not about to give up... Chris