Hi Chris and all, thank you for your reply. Anyway, last evening I found the problem which was, needless to say, on the W$ machine. Infact to switch from "work" (DHCP, DNS, Gateway and so on) to "home" (fixed IP and stop) I was using a small sw called Netswitcher, supposed to allow switching between different network configuration (yes I know it's in Beta release). Everything worked as soon as I wrote again by hand the network config. on W$. Anyway, when I accessed hardware config from yast, in order to check the registration the 3com 3c905c in the network cards, I couldn't list it. YaST field was highlighting PCMCIA card... but the card was working properly. Thanks everybody, best regards, Stefano Chris Reeves wrote:
Stefano Papini wrote:
Still a "poor" question.
My SuSE6.1/2.2.14 desktop works sometimes as a ftp-server for my company W98 laptop, so I can upload files from SuSE. I configured through YaST my 3com, assigned a IP (192.168.0.1) and everything went fine (my laptop was configured as 192.168.0.2): ping and ftp good.
Then I upgraded YaST and all the update rpm available for 6.1. (Now I have no details because now I'm at work while the SuSE is at home).
Self-ping is ok but ping towards the laptop (configured as 192.168.0.2) fails. Of course any ftp fails.
More it seems from the screen that YaST doesn't see the 3com as recognized. (yet the older version worked).
Is there the possibility that changing YaST ore updating some package has modified something?
I'm not sure.
Are you saying that your 3Com isn't detected? Does it not mention it in the bootup messages (to see them, type 'dmesg')? If not, is the module loaded? What type of card do you have?
Waiting for more info... Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/