streeter

I don't use firewall builder, so am guessing... From Release Notes So if you enabled any of the above options, perhaps you need to patch the kernel/iptables? Or not use the said options? Like I said just guessing, but may be a starting point for you. Chris

Then unless I am missing something, you need to check your physical network. First unplug everything and check you have the correct cables - the coloured wires should be 'straight through' ie pin 1 to pin 1. 2->2, 3->3 etc. If pin 1 goes to pin 3 (and 2->6), you have a crossover cable. Make sure you have not plugged a straight through cable in to the hub uplink port. Try different hub ports. As you have only 2 computers to join together, you can use a crossover cable and connect the computers directly to each other - this will eliminate the hub - perhaps that is faulty. Try new cables If this doesn't work, I have run out of ideas for now... Chris

OK - eth0 is up, your routing table is correct, and flashing lights mean something is getting out - fine so far. Can you ping FROM windows? We need to know if windows can talk to Linux. If you are unsure how to do it, go to start->run and type "cmd" (in winXP, for 9x type "command") Then a terminal window will appear. Type "ping 192.168.0.1" followed by "ping 192.168.0.5" Chris

Could we have some output from the following, so we can check what is working, and what isn't... 1) Output from "ifconfig eth0" 2) Can you ping Linux from the windows machine? Also windows from the windows machine? 3) You should still have a resolv.conf for good measure - you may want to do something that doesn't use the proxy. It will only be used when necessary. 4) You still don't have a default route? Put the following line at the end of /etc/rc.d/rc.local: route add default gw 192.168.0.1 eth0 Then reboot and send output of "route -n" 5) Are the hub link lights on, and do they flash when you try to ping? That'll do for now.. :) Chris

Pretty sure that once samba is installed, it will start automatically at boot. If not, use drakxservices or some similar tool. Apart from the wizard (get to it from the mandrake control panel) you could also have a look in the main configuration file - it is very well documented, with several examples - all in the config file! The file is in /etc/samba/smb.conf - as long as you back it up first - type (as root) cp /etc/samba/smb.conf /etc/samba/smb.conf.bak you can play around to your hearts content!! - Go on, do it the hard way!! Actually, it is not that difficult, as I said, it is well commented. Start off with changing the workgroup if you need to, set up a simple share, and go from there. You could always run the wizard first, and see what it does. If you break something, just do cp /etc/samba/smb.conf.bak /etc/samba/smb.conf and all will be as it was again! After changing something, either wait for a minute for samba to re-read the file, or type samba restart for instant results. As with anything Linux, a little reading and preparation goes a long way. BTW - this thread is getting very long - if you need further help, best start a new one so that others in need will be able to find it. Have fun Chris

Glad it's working - phew!! The windows workgroup name is for the smb protocol - it just groups bunches of PCs together. ie.several PCs will share the same workgroup name. Default with win 9x was WORKGROUP. The hostname is for the TCP/IP protocol - a unique name for each PC, separate from the smb workgroup name and can be anything you like - so you could call your PC WORKGROUP if you like, but it might get confusing for us simple humans.... In windows network neighbourhood you would open the workgroup WORKGROUP, only to be presented with a PC also called WORKGROUP... For reference, a fully qualified domain name (FQDN) is your hostname followed by your domain name. My domain is showerail.com and I call my main PC linux, so my FQDN is linux.showerail.com. Another PC may be called streeter.showerail.com or glore.showerail.com. On your network you may have glore.mylan.home or anything you like. The book rute will explain it all better than I can.... Chris

Try typing drakconnect at the command line. But if your connection is working, I wouldn't recommend running it - something may break - see other threads here.... Chris

The source will probably be somewhere under /usr/src/RPM. If you enter the IP address, DNS/hosts is not used... I assume you can ping between these boxes? Chris

Try moving the cards to different slots. If you type "dmesg | less" you will get the startup log, or look in /var/log/ Chris

All "iptables -t nat -D PREROUTING -i eth0 -j loc_dnat " does is remove a table entry - if the entry is no longer there (the result we want) you will get the error. So the result is the same - the entry is gone. Did you put the "iptables -t nat -D PREROUTING -i eth0 -j loc_dnat " at the end of /etc/rc.d/rc.local? If not, do it now and reboot. Then try it out. Then post output of "iptables -nvl -t nat". Forget webmin and squid for now - you don't need them. What we are trying to do is stop your PC from automatically redirecting http requests to squid. The above command should do that, if I got the syntax right... Chris

(copied and edited from another of my posts) I think perhaps the easiest thing to do though would be start from scratch manually (what have you to lose?): Type drakxservices in a console as root. Click Stop and uncheck "On boot" dhcpd, squid, netplugd and named if they are there and running. This will turn off some unnecessary and possibly broken servers. Then edit /etc/sysconfig/network-scripts/ifcfg-eth0 - the entries should read : DEVICE=eth0 BOOTPROTO=static IPADDR=192.168.0.5 NETMASK=255.255.255.0 NETWORK=192.168.0.0 BROADCAST=192.168.0.255 ONBOOT=yes MII_NOT_SUPPORTED=yes /etc/resolv.conf should have valid nameserver addresses - put the address of your ISPs nameserver (get it from windows?) at the top. eg nameserver 195.20.224.165 (this is a valid nameserver you can use for testing - it belongs to onetel in the UK, so you should use your own ISPs nameserver - check their website) The default gateway goes in /etc/sysconfig/network: HOSTNAME=yourhostname_goes_here #eg linux.mylan.home NETWORKING=yes GATEWAY=192.168.0.1 Then type "ifup eth0" . Then try pinging windows from linux. If it doesn't work, you need to check the cables (how are the machines connected? Through a hub/switch, or directly with a single cable?) and Windows firewalling. Check to make sure it all works across a reboot. Think that coves it all - apologies if I left something out... Let us know how you get on, including the output of "route -n" Chris

Oh, the book you need is called rute - it is on your install disk. Type "urpmi rute" this is a general Linux book. You can also type "<whatever you need to know> howto" in google eg iptables howto or "man <command> on the command line. Chris

Whoopeee!! What we have done is set up basic IP networking - windows networking is another layer on top of this, and uses the smb protocol. For this, under Linux, we need the samba package (install with "urpmi samba"). I also recommend the smb4k package, a sort of network neighbourhood for Linux. If you have any questions about samba set up (try the wizard first, I think it is more reliable than the networking one!), start another thread here. I too am 40, and share my time between selling shower curtains on-line (boring) and fixing PCs on the Isle of Wight (much more interesting). Oh and spending far too much time looking at forums.... :) Chris

¿Qué es un DNS? Para empezar a utilizar un DOMINIO, es necesario que exista un servidor reconocido por la Red que guarde la relación entre el número IP y nuestro dominio, a estos servidores se los llama "DNS" Servidor de Nombres de Dominio (Domain Name Server). Esta relación entre dominio y DNS se hace efectiva en el momento de la "registración" del dominio en las páginas habilitadas. Por ejemplo los DNS de FiberTel son: dns1.cvtci.com.ar IP Nº: 24.232.0.17 dns2.cvtci.com.ar IP Nº: 24.232.0.18 Hey, I'm learning new languages here!! I think this means you put nameserver 24.232.0.17 nameserver 24.232.0.18 in /etc/resolv.conf and the dns entries in windows networking. Your hostname can be anything you like - linux.mylan.home for instance Chris

Not another one!!! This is getting to be a common story. What am I missing here? Mandrake network wizard is doing/not doing something, and I don't know what... Your Ip address is OK, your net card is OK, your routing table is OK. (by the way, "route -n" will get rid of that delay, by not using hostname lookups) So, all I can ask for is the output of "iptables -nvL" , iptables -nvL -t nat" and what is at 192.168.0.1 - a router/modem/another PC ? Should I write a "setting up Mandrake networking without wizards HOWTO"!! Chris

This is getting frustrating... Right - we have got your Ip address on the computer OK (192.168.0.3), and your network card is working because you can ping it. You have no firewall rules, so that's not stopping it working. I don't think the modem has a firewall (and you reset it anyway), but please check the manual. Please post your routing table - type "route -n" as root. All that remains after that is the cabling... Try unplugging the cable, then plugging it back in again. Are you using the cable that came with the modem? Or is it a crossover cable? In a normal cable, the coloured wires all go to the same pins at each end, eg orange/white is pin 1 on both ends, pin 2 is orange. (these 2 pins could also be green/white & green, but the point is, they are 'straight through'). In a crossover cable, the cables at pins 1&2 at each end go to pins 3&6 at the other. Chris

1) Yes - a static Ip address will work fine 2) If you were using the linux dhcp server, you may not have a DNS server address set, in which case, you need to check your ISPs website. If you have no luck, tell us what ISP you use, and we can look it up for you. The address I gave in the example should work (my ISP, located in Britain so not perfect) if you cannot find your own. If there is a DNS address set in windows XP, you will find it in the network properties - Right click on 'my network places', select properties, right click on your local area connection, choose properties. Select 'internet protocol' and properties. Here you will see if you have DNS server addresses set, or 'obtain DNS server address automatically'. It is similar in win 9x. The computer uses a nameserver to resolve (hence the file /etc/resolv.conf where we store this address) human readable addresses (eg www.google.com) into IP addresses. So each time you request, for example, a web page the computer first asks a nameserver for the IP address. You can run your own, but I am trying to keep things as simple as possible for now. You can add a nameserver and proxy server later if you like, when (if!) it all works. Chris

Have a look here: Linux Gazette Haven't tried it though... Chris

Don't know enough to say "this is your probem"... I come from the Isle of Wight - a small island just off the South coast of the UK. Love the Internet - don't you? Makes the world a little smaller :) If you send me $$$loads I will fly over to set your PC up :D Ok - back to business... You are right - you don't need to enter an Ip address, if it is getting one (probably from the router, but mdk internet connection sharing installs a dhcp server also) via dhcp. I think perhaps the easiest thing to do though would be start from scratch manually (what have you to lose?): Get the network config from Windows - especially the nameserver and default gateway. Type drakxservices in a console as root. Click Stop and uncheck "On boot" dhcpd, squid and named if they are there and running. This will turn off 3 unnecessary and possibly broken servers. Then edit /etc/sysconfig/network-scripts/ifcfg-eth0 - the entries should read : DEVICE=eth0 BOOTPROTO=static IPADDR=192.168.1.104 # or 102, or whatever you like NETMASK=255.255.255.0 NETWORK=192.168.1.0 BROADCAST=192.168.1.255 ONBOOT=yes MII_NOT_SUPPORTED=yes Then edit /etc/sysconfig/network-scripts/ifcfg-eth1 - the entries should read : DEVICE=eth1 BOOTPROTO=static IPADDR=192.168.0.1 NETMASK=255.255.255.0 NETWORK=192.168.0.0 BROADCAST=192.168.0.255 ONBOOT=yes MII_NOT_SUPPORTED=yes You may also have to set windows up to a static address (192.168.0.2) with 192.168.0.1 as the gateway, and possibly your ISPs nameserver(s) in the DNS set up. /etc/resolv.conf should have valid nameserver addresses - put the address of your ISPs nameserver (got it from windows?) at the top. eg nameserver 195.20.224.165 The default gateway goes in /etc/sysconfig/network: HOSTNAME=yourhostname_goes_here NETWORKING=yes GATEWAY=192.168.1.1 Then type ifup eth0 followed by ifup eth1. We then need to set up packet forwarding: echo 1 > /proc/sys/net/ipv4/ip_forward iptables -t nat -F iptables -t nat -A POSTROUTING -o eth0 -s 192.168.0.0/24 -d 0/0 -j MASQUERADE The nat module should get loaded automatically. Then try it all out. If it works, you can put the iptables commands at the end of /etc/rc.d/rc.local. Check to make sure it all works across a reboot. Think that coves it all - apologies if I left something out... Let us know how you get on, including the output of "route -n" , "iptables -nvL" and "iptables -nvL -t nat" Then we can fix anything else not working... Chris

That just means iptables is not installed. Edit>> Wait! no it doesn't - it means iptables IS installed, but the nat table module is not loaded. Chris

You are right - you don't NEED the firewall - Like I said, I just tried it on a fresh install. The wizards are indeed hopeless... The routing is OK, apart from the default route - network 192.168.0.0 and netmask 255.255.255.0 is class C. it's OK to use the zero in the third octet. If you mean the odd entry in resolv.conf (search 168.0.1), I am assuming hugosantos has that as the domain name?? eg linux.168.0.1 ?? otherwise just comment out/delete this line. This wouldn't stop a ping by Ip address anyway. Chris

What I really meant was "please post the output of telnet <linuxbox> 25" from the windows box Don't know your knowledge level here, so don't be offended, but you can actually send email using telnet, and the error messages may help. Have a look here: telnet session There is a setting in /etc/postfix/main.cf - inet_interfaces which allows you to send mail on only those interfaces specified. The default is inet_interfaces = all, so you could check it is not changed. The main.cf file is well commented. chris

Or do the startx -- :1 thingy as above or 'start new session' from the start menu, then lock the screen (in start menu) for yourself? New session will be at <ctrl, alt, F8>, and any user can log in Chris

smb4k is very good - install it if you can find it. You probably need to add new software sources - go along to http://urpmi.org/easyurpmi/ and follow the instructions. This will also set you up for security updates etc... Chris

Don't see how webmin or swat could trash a graphics driver - that's more a windows thing :D Probably coincidence. If it happens again, don't reinstall - these things can almost always be fixed under linux. Start by making a backup of /etc/X11/XF86Config-4 RIGHT NOW. Iphitus is probably right - try the samba wizard in the servers section of mandrake control centre (mcc) - will probably be more straight-forward. You may need to install the server wizards with "urpmi wizard" or "urpmi drakwizard" should do it. Probably. Chris