I'm having a real problem with intermittent ssh disconnections?It's the same thing regardless if it's over ethernet or wireless, and nfs shares don't have any problems at all.
View 1 RepliesI am using OpenSuse 11.3 and Network Manager is giving me a headache by not connecting to WEP based wi-fi network.It works in a wi-fi at my office while at my home, it shows / detects the network but keeps asking me over and over.
View 3 Replies View RelatedI'm trying to setup PS3 media server on my new OpenSuse 11.2 and I'm being unable to connect to the PS3. The multimedia server seems to being working ok, only it has not appear on XMB.
I've been searching on PS3 Media Server forums and try a couple of solutions regarding /etc/hosts and adding full qualified domain name of server to it, but it doesn't seems to work.
I have a Ubuntu server (10.10) setup with apache and is being port NAT'ted via firewall from outside to the webserver.I am able to access the webserver from inside LAN but not from outside. NATs are working fine because I can see the traffic come through on tcpdump but the webserver will not respond to the request from outside ip address.Here are the tcpdumps.
10:11:58.939005 IP 12.xxx.xxx.6.10146 > 172.16.2.100.80: Flags [S], seq 3098920688, win 65535, options [mss 1380,nop,nop,nop,nop], length 0
10:12:01.898852 IP 12.xxx.xxx.6.10146 > 172.16.2.100.80: Flags [S], seq 3098920688,
[code]....
I installed 11.2 on an older HP Laptop which was running XP without any issues. Durring the install, the update processe failed (presumably unble to connect to respository). I am usind a wired connection and the nic is connecting to my router and is recieving an address via DHCP. I am also able to ping the workstion from the router's Web interface. However I am unbale to connect to the internet.I have turned off the Suse firewall via Yast and checked the settings against another computer running ver 11.1 .Everything appears to be correct but no joy.
View 9 Replies View RelatedWhen I try to update with YaST2 or zypper it complains about being unable to connect to the repo's
I'm getting this error with all repo's except for one i've added manually (google chrome)
Am I doing something dumb or are the actually down?
is there a shortcut to open konsole?
I did a fresh install,I also enable the networkmanager.after installation,my wireless unable to connect to my router . when I click to connect , it prompt for password then after that nothing happen.
View 8 Replies View Relatedi've just installed opensuse 11.2 everything is working fine but i'm unable to connect to the internet through my adsl modem the network is shown to be active but after i configure the dsl connection i can't see any option from where to connect
View 1 Replies View RelatedI want to connect my mobile LG Gu285 using data-cable to connect to the internet in OpenSuse 11.3 but the OS is not detecting mobile's usb data modem. I used sudo wvdialconf create command to configure my phone's modem but no modem is detected. I configured bluetooth modem in "rfcomm1" and got success in connection but after a restart I am unable to connect again, throwing error "Modem not found".
View 7 Replies View RelatedI have Ubuntu 10.04 x86 installed, trying to get teamspeak 3 beta30.I have followed this guide: http://robert.penz.name/296/howto-in...u-10-04-lucid/
And can not get my network setup correctly to allow people to connect externally from my LAN. I have forwarded every relevant port I could find to the computer hosting TS, I forwarded them first as their respective protocols, and then as the combined UDP/TCP. I tried Forwarding single port numbers, and then port ranges.I have also tried uninstalling selinux.I have tried connecting directly to my cable modem with the server.I had this working perfectly three months ago with all the same software, using the same guide I listed above.The only thing I can imagine has changed is my operating system itself with system updates.
My network looks like:
Comcast cable modem--->Netgear WNR3500L Router----->Ubuntu 10.04 x86 desktop edition
what else I could possibly check? I can connect to and manage the TS server fine using localhost:9987 or 192.168.1.x:9987, it just wont allow any connections from outside the network.
I am not able to connect to the Remote VNC Server..Error: ConnectToTcpAddr: connect: Connection refused.
View 6 Replies View RelatedI'm using something like telnet [URL] 25 and it comes back as not being able to connect to host on port 25. I don't have port 25 blocked anywhere. I turned off the firewall and even opened up port 25 on the hardware firewall router. If I ping it I can connect.
View 2 Replies View RelatedI need to install Yum, but does not connect to the server.
Code:
Resolving package dependencies...
Here is the list of Zypper
Code:
I have an openSUSE 11.2 and I was trying to connect to a FTP server from Dolphin application but it didn't work. (I used ftp://<IP ADDRESS> in the address field)
From CLI or using FileZilla I can connect to that server.
What could be the cause of this strange behavior?
Upgraded two machines to 11.3 in the past 2 weeks. NFS is broken on both, in different ways. The problem I'll mention here is that the nfs server is running, but clients can't connect.
The server is running:
tinderbox:~ # /etc/init.d/nfsserver status
Checking for kernel based NFS server: idmapd running
mounted running
statd running
nfsd running
It has a valid export list:
tinderbox:~ # showmount -e
Export list for tinderbox:
/usr/local/share/common 192.168.1.0/24
The export exists:
tinderbox:~ # ls -lR /usr/local/share/
/usr/local/share/:
total 4
drwxrwxrwx 2 root root 4096 Jan 2 12:10 common
/usr/local/share/common:
total 0
-rw-r--r-- 1 root root 0 Jan 2 12:10 test.txt
But attempts to mount the export are unsuccessful, both from the local machine:
tinderbox:~ # mount.nfs 192.169.1.200:/usr/local/share/common /mnt -v
mount.nfs: timeout set for Sun Jan 2 12:14:19 2011
mount.nfs: trying text-based options 'addr=192.169.1.200,vers=4,clientaddr=192.168.1.200'
mount.nfs: mount(2): Connection timed out
mount.nfs: Connection timed out
...and from an OpenSUSE 11.0 machine.
moira:~ # mount.nfs 192.169.1.200:/usr/local/share/common /mnt/tmp/ -v
mount.nfs: timeout set for Sun Jan 2 11:52:17 2011
mount.nfs: text-based options: 'addr=192.169.1.200'
mount.nfs: Unable to connect to 192.169.1.200:111, errno 110 (Connection timed out)
mount.nfs: mount to NFS server 'rpcbind' failed: timed out, giving up
I've had NFS running on my local network for over a decade, and never had problems like this before.
until 2 weeks ago I had o.S11.3 on both my Siemens and Asus laptops. I have installed NX No Machine. ( I know it's not open source,I am using the free version). With commandline ( root) /usr/NX/bin/nxclient I was able to connect to the other machines. I got Qt: Locales not supported on X server, the NX menu popped up and I was able to connect by inserting resp codes. After fresh install of o.S.11.4 on the ASUS the commandline (root) answers:
xlib: connection to":0.0" refused by server
xlib: No protocol specified
nxclient: cannot connect to X server:0.0
The ASUS can still be reached from the other machines (one with o.S.11.3,the third one with o.S.11.2 ) SSH ( Lan)connections are all working forth and back between the machines, even to and from Win XP, however only from Win 7 on the ASUS, but that's a Win7problem. Comparing the installed xorg-x11- server-extra : on o.S. 11.3 Additional X servers ( Xmdx,Xephir,Xnest,Xvfb ) ,on o.S.11.4 the Xvfb is missing, might that be the reason?
So a while back I was able to mount a directory from my OpenSuse server as a NFS on an Esxi server. After restarting the Esxi server, the NFS became inactive and I was unable to remount it. The error given was that the Esxi client was unable to connect to the Suse server. I was looking into the showmount -a command on the Suse server and it showed the mount point on the Esxi server. Could this be causing the Suse server to reject new attempts to mount the directory? What else can I try to fix this problem? Also I should note that both servers can ping each other.
View 2 Replies View RelatedI have steup samba shares on my Susi pc. I get to the point where the server asks for a password for the user I have on the Susi box but when I enter the password it fails to connect. tried to add the user, password and enabled the user in the samba conf file. But not sure where it should appear I give below the smb.conf file:
# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
[code]....
I was fiddling around and unchecked the lda api thingy when I was experimenting with TLS now I can't connect to the ldap server ...is there any way to get it back.
View 1 Replies View RelatedWith SUSE-9 I used pptpconfig to connect to a Windows VPN Server.With openSUSE-11.3 I created a VPN Network Connection,however I have no idea how to start the network connection.
View 1 Replies View RelatedI have x11 forwarding enabled in /etc/ssh/sshd_config on a suse 11.2 32 bit box running kde I can open x apps on a windows machine using xming and putty just fine, but when I boot the same machine into suse 11.2 64 bit using kde and try using konsole I get: cannot connect to x server
The command I'm using to log in is: ssh -X -l username host I doubt the problem is with the server I'm logging into or it wouldn't work in windows, not really sure what to look for as I've never had a problem using x11 forwarding from a linux client before only windows ones
I have a Thecus NAS with nfs support running. Now I switched from OpenSUSE 10 to 11.2 on the client side and aren't able to mount my nfs shares. With SuSe 10.0 I didn't have any problems.
The /etc/exports:
/raid/home_nas1 192.168.0.24/31(rw,no_root_squash,sync,anonuid=99,anongid=99,no_subtree_check)
/raid/soundandmore 192.168.0.24/31(rw,no_root_squash,sync,anonuid=99,anongid=99,no_subtree_check)
On the client side I'm able to see the shares:
showmount -e nas1
Export list for nas1:
/raid/home_nas1 192.168.0.24/31
/raid/soundandmore 192.168.0.24/31
The client address:
inet addr:192.168.0.27
I'm using nfs-3:
mount -t nfs nas1:/raid/soundandmore/mnt
mount.nfs: access denied by server while mounting nas1:/raid/soundandmore
I have setup an dhcp server wich allows ICS, and a samba server as a PDC. I can access the shares from windows if I type the server Ip (ej. \192.168.0.1), however if if write the address (ej. \dbaserver) I cannot access them.If I type ping dbaserver on a command prompt, it returns 127.0.0.2 not 192.168.0.1, what could be wrong. I asume because of this I cannot join the domain also.
View 4 Replies View RelatedI just switched from Ubuntu to Fedora 13 because I was unable to get Ubuntu to connect to wireless networks. I tried everything suggested in help and forums, and kept getting "Bad Password" with WICD and Network Manager. Now, with Fedora...I still can't connect.
Problem #1: The guide says to "...make sure that the relevant wireless interface (usually eth0 or eth1) is controlled by NetworkManager," and that I do this via: System>Administration>Network
However, there is no Network option under System>Administration.
Problem #2: I open Network Manager, which displays a list of networks. I click on mine, configure it with WPA and the right password, and it fails to connect: "The network connection has been disconnected."
I was programming much in windows and I slowly get used to linux, I'm using SUSE 11.2 as a server in my home network. I about 10 windows-pc's in my network, which is structured as following: Very simple router (no dhcp) -> Switch -> Win1, Win2, .., Suse, I already managed to set up the DHCP server, and it works like a charm, I'm not able to get in the internet with the Windows PC's. This is especially strange if you consider the settings:
[code]...
I tried pinging the gateway from both suse11.2 and win but it failed. Pinging win7 to suse and other way around is possible. internet works on suse11.2, but it doesn't works on win.
I'm unable to connect to a particular home wireless network under Fedora 9, although I can connect to it using WinXP on the same machine. My Fedora installation is able to connect to my college's unsecured wireless network, so it's not a driver issue I think.It seems to be an authorisation issue, as I'll describe below, but there's one other thing that's bothering me. The SSID for the network I have problems with is for some reason not listed in Network Manager's drop-down list, nor is it in the output of iwlist wlan0 scan. But I'm pretty sure it's not a "hidden" network - I don't know exactly how those work, but I helped the owner of the wifi network in setting it up, and don't remember doing anything that would make it hidden. As far as I can remember, Windows found the network automatically without having to be told the SSID. What's the best way to confirm whether it's a hidden network or not?
Anyway, I try to connect by selecting connect to other wireless network in Network Manager, and entering the SSID. As far as I can tell from the error messages below, the machine does contact the network and attempt to connect, but I'm not authorising myself properly. That may be a completely wrong diagnosis, but hopefully someone can see from the below info whether it's correct or not.I'm not sure which option to use for "Wireless Security": at the time we set up the network, it gave us a Hex WEP key of 26 characters, which is 104 bits. But none of the options in Network Manager's list match that. Here are the options it has, and the error message I get with each one:None - if I select this, it fails to connect, with no error message.
WEP 128-bit passphrase - if I select this and attempt to use my 26-character WEP key, it brings up a new dialog, saying "Passwords or encryption keys are required to access the wireless network [SSID]." It has a drop-down box labelled "Wireless Security", but this time the only option is "None", and the connect button is disabled, I can only click cancel.
WEP 40/128-bit hex - as above.
WEP 40/128-bit ASCII - The connect button is disabled when I try to use the WEP key, as the string is too long. Despite the fact that it says 40/128-bit, it actually accepts 5 and 13-character strings (40 or 104-bit). Since I've got a 104-bit hex key, I tried converting it to ASCII, but it consists of mostly unprintable characters, so I'm not sure there's any way to actually enter it into the textfield. I might have done something wrong here, so I've put my code below to see if anyone can point out a mistake.
LEAP - requires a username, not applicable here I think. Windows doesn't need one, and we don't have one from when we set the network up.Dynamic WEP (802.1x) - requires username, private key and various other things, all N/A WPA & WPA2 Personal - Brings up a dialog with the same text as for "128-bit passphrase", but this time "WPA & WPA2 Personal" is the only option in the drop-down list, instead of "None". It asks for a password, so I just enter the hex key again - now it asks for the password for the Gnome Default Keyring, which I don't think I've ever set up. Don't know if I can go any further with that, but my understanding is that since we were given a WEP key when we set up the network, WPA will be N/A.WPA & WPA2 Enterprise - as Dynamic WEP. N/A.Hopefully that's enough info that someone can help diagnose the problem. Some of the behaviour of Network Manager described above doesn't make sense to me, and I'm wondering if it's buggy.
I am running opensuse with LAMP, and this is my first time setting up this type of server (usually am a windows junkie) My problem i am having is that I am unable to view my website from outside the local network. I have setup my router for a dynamic dns and forwarded all the ports through the router and the local firewall. I ran the apache setup through YAST2 and everything seems fine locally but when i attempt to access it elsewhere its not connecting. computechsolutions.dyndns.biz is the dynamic dns address i have setup through my router.
View 2 Replies View RelatedOn one machine I have OpenSuSE 11.4 and the other is Windows 7. From OpenSuSE I can connect to the Windows 7 machine running Tight VNC using KDRC and no problems. But I get a message of 'Failed to connect to server (192.168.1.1)' when I go from the Windows machine to the OpenSuSE machine. ON the OpenSuSE machine, the firewall has VNC and VNC Sercver allowed in the firewall. In the Remote Administration, 'Allow Remote Administration' is checked and Open port in firewall is also checked. Why can I not connect? Also, how do I set what the password is on the OpenSuSE machine?
View 9 Replies View RelatedI am not able to connect to network after update F13 to 2.6.34.7-61. Because there is "no netwokr decvice" IAW network manager. There is nothing in system log that abonormal. But, there is a fail initialization in the boot message. "applying firewall rules: iptable v1.4.7:Ip6table-restore: unable to initialize table .filter error occur at line 3 try Ip6table-restore -h or Ip6table-restore -help for more detail"
so, I tried the comment at terminal with root clearance, it just give some feed back about how to use this command. When I tried out other options. none of them work. There is no feed back form the terminal other than previous display and blanking cusor.
I assume it was the firewall preventding me to connect to network. And I complete disable SELinux and reboot. Problem remain, no network device. Check network device driver. There all inplace. Tried using old kernel, unble to boot up X window, presumably old driver has been deleted.
BTW, after two consecutive update failure (2.6.34.7-54 kernel panic VFS? problem, 2.6.34.7-61 no network connection), I assume Fedora Quality should consider review their update release process. Since the probability of fedora releasing bad update is increase a lot after fedora 11.
I see the network applet in the panel which shows that I am connected but I cannot access the net. I found out that I had to do this in firefox
about:config --> IPv6 --> disable.IPv6 true
With this tweak I was able to connect to the net. But when I use the Update Manager or Synaptic I am not getting connected, even if I use the cli and do
Code:
apt-get update: I cannot connect. When I do