SilverSurfer60

The answer appears to be the wpa settings as you say. I'm sorry but I don't have the solution but I'm sure there will be someone along soon that can resolve this for you.

The next thing you can do is run dmesg in a console and look for entries relating to your network connection. If you're not sure what to look for post the output and we can take a look. You shouldn't need to re-install ;)

Sounds like your network service is not set to run at boot time. A check in mcc->system->services should tell you. Just make sure there is tick in the On Boot box.

You can also get to the menu editor with a right click on the start button, either the star or the mandriva button whichever you have. Just an alternative for you, as for the information given it's quite correct.

Ah well I tried. Sorry It didn't work out for you. If you weren't surprised I was. :D I'm out of ideas now for Debian anyway. Looks like you will have to restart your server until someone comes up with something. I'll carry on

As I was unable to re-create your fault 'cause I'm on a different distribution I changed tack and took the suggestion from Aoishin and setup autofs. It took a bit of working out because most of the howto's dealt with local shares. However I got it working fine in the end. It has solved a small problem for me, so it probably would be the route for you to go. It is quite simple to set up and not much in the way of padding. To start with you will need to install autofs unless it's installed by default, mine wasn't. After installation you will have a new sub-directory in /etc called 'autofs' in this directory besides a couple of files you don't need to touch are two which you will need to edit. The first one is named 'auto.master' there is a bunch of lines in there commented out, leave them and make sure you have one pointed to the second file named 'auto.misc' this is the business file. In this file is an example, ignore it, and comment it out. Now you will list the directories on your network that you want to access :- docs -hosts pc1:/home/qandd/docs One line for each share. The first column designates the mount point. In the example above the mount point will be '/misc/docs' The second column tells autofs you are using the network and third column is where the share is on the server. That's it. All the permissions etc. are just the same on the server as they are for the nfs mount. Now a couple of points are things you can tailor for yourself, one is in the file auto.conf and it is the timeout= Change this to a reasonable length of time for you. It is in seconds and tells the system how long to wait before disconnecting from the server. You can connect again anytime you need to access the directory. The next thing you can tailor is the name of the file 'auto.misc' you can change the extender to what you want, something not in the directory tree preferable. This extender forms the root for your directory. Of course you will need to alter auto.master to point to your file otherwise it will not be read. If you feel like having a stab at it do so. I think you will be surprised. I was.

I understand what is not happening now (I think), it needs some more trouble shooting so I'll post back when I have something for you to try, unless someone else solves it for you in the mean time. :P

Which now leads me to believe the execution order of start-up scripts is suspect, as you mentioned once before. If Debian has the same sort of start-up as Mandriva you need to check /etc/rc3.d/ for a link to the execution of a script that starts your nfs-kernel-server, this same link should also be in /etc/rc5.d/ If you don't know what I'm talking about please post the contents of /etc/rc5.d using the command ls -l and likewise the contents of /etc/init.d/ If you do understand the contents of the /etc/rc[whatever number].d then changing the execution order of the link may rectify the problem. i.e. let's say in /etc/rc3.d you have a link named S2nfs-kernel-server then rename it to S99nfs-kernel-server I hope all this makes sense to you. That is if you would like to solve it. ;)

I'm on.

I'm on 2007.1 and I have one. It only has an alias in it, and I didn't put it there! :huh:

I was thinking along those lines in that your shutdown scripts may need a little tweak to ensure that the shares are unmounted, You are quite welcome. It gives they old gray matter something to do.

For simplicities sake let's stay with PC1 as a server and PC2 as a client. Maybe a careful look through your syslog on PC2 after closing down PC1 and look for errors relating to your nfs file shares before closing down PC2, and again after starting up PC2. Almost certainly there will be a record in the log file that should point you in the right direction. Assuming you do have system log files in Debian, it's a long time since a played with that OS I can't remember.

What I see is as follows:- When you close down PC1 before PC2, PC2 does not have indication that PC1 has shutdown and therefore still has an entry (lock) in /etc/mtab and is not unmounted. When you come to reboot PC2, it tries to remount an already mounted network file system. Hence the permission denied. If you did the opposite and shutdown PC2 first I think you would find the opposite happening. This is difficult to explain and I don't know how you would get round it. I have to 'unmount' and then 'mount' whichever PC I shutdown last. Otherwise I cannot access whichever PC I shutdown first. Cor my head is shutting down with this one. :P

I'm pleased it all worked out for you. What did you do in the end?

What you are trying to do can be done with mandriva, I do this very same thing myself with three pc's. The only thing to watch out for is that you are not trying to share the same directory back to the server. I tried that by mistake. Other than that no problem. As I said I'm not familiar with how debian does this so I can't comment any further on that one.

Wouldn't it be a lot less messy setting both machines as a client and server? That way you have access to what ever you want to share on either pc. I forget how debian handles this, but it seems logical to me.

Take a look at mencoder while going through the 'man' pages.

Very interesting report. I am quite surprised at the ones charging for access rule what system you have to use.

There is quite an extensive 'man' for lame, have you had a look at it? Folks do tend to forget there is a lot of these pages an sometimes they will answer a lot of questions.

It may be that libQtDBus.so.4 is not listed as a package, rather a file within a package. Sometimes I use mcc and do a search for files with the name I'm looking for.

To link two pc's without using a router you will need a crossover cable ie. The send and receive wires are crossed over.

OK try this it worked on one card for me. Add to /etc/modprobe.conf alias etho wlan0 It shouldn't be needed but hey if it works!!

From what I see so far everything seems in order. Now check /etc/modprobe.conf and you should have a line 'alias wlan0 ndiswrapper' if it's not there then add it at the bottom of the list. Then check '/etc/sysconfig/network-scripts' for a script 'ifcfg-wlan0', if it's not there you will need to add one. I assume at this point you know how to do that, remembering to chmod to a+x It should contain all your connection properties as in the example below. I have blanked out certain private details. DEVICE=wlan0 BOOTPROTO=dhcp ONBOOT=yes METRIC=35 MII_NOT_SUPPORTED=no USERCTL=yes RESOLV_MODS=no WIRELESS_MODE=Managed WIRELESS_ESSID=ANY WIRELESS_ENC_KEY=xxxxxxxxxxxx IPV6INIT=no IPV6TO4INIT=no DHCP_CLIENT=dhclient DHCP_HOSTNAME=xxxxxxxxxx NEEDHOSTNAME=no PEERDNS=yes PEERYP=yes PEERNTPD=no If all goes well you should be able to restart your network and have a favorable result with the command 'ifconfig' in the console. Excuse me if I missed anything no doubt I will be told about it :P) and best of luck.

Will you post the reply to ndiswrapper -l and that is -L not -I and run as root. As an after thought please check in '/etc/ndiswrapper' and make sure you have the firmware i.e. 'bcm4318.sys' in the same directory as the driver file.

Sorry to hear you're having so much trouble installing a wireless card. I have no experience with 64 bit but I have had a great deal of experience with wifi cards. A visit to this site Click Here should reveal the best driver to use for your card via ndiswrapper. Of course you need to know what chipset the card uses, even though it says broadcom you may need to have a look on the chip itself as there are a good many different broadcom chips. When setting up a network connection you need to select wlan0 as the network adapter as auto detection will come up with eth0 as default. I have set up a good few network cards using drakconf in this manner and all of them are now working, at least three at the moment. I hope this is of some help to you.