Sponsored Content
Full Discussion: Network issue in SLES11.2
Operating Systems Linux SuSE Network issue in SLES11.2 Post 302828439 by Corona688 on Tuesday 2nd of July 2013 12:31:33 PM
Old 07-02-2013
These cards are known to have problems, I suggest using another NIC if possible.
 

10 More Discussions You Might Find Interesting

1. Ubuntu

Network issue

I have a Ubuntu linux (Ubuntu 6.06) at home. I have a ADSL modem (eth0) connected to it for my Broadband connection. It all works fine when the system gets started. But, when I receive a call, the link goes off. And then I lose my internet connection. I tried ifup/ifdown to bring the connection... (2 Replies)
Discussion started by: ranj@chn
2 Replies

2. Solaris

Network interface issue

Hi All, I want to configure network into my system. i tried following in to configure the interface to find the name of interface #prtdiag |grep net i got following 0 PCI-1 33 1 network-SUNW, hme then i tried following #prtconf -v |grep net network, instance #0 (6 Replies)
Discussion started by: kumarmani
6 Replies

3. SuSE

SLES11 - RAID6 all disks marked as Spare

Hello, After a replacement of the motherboard of my server, all disks belonging to a raid6 are now marked as spare. Is there any way to mark those disks as active and restore the raid6? $ cat /proc/mdstat Personalities : md1 : inactive sda1(S) sdk1(S) sdj1(S) sdi1(S) sdh1(S)... (0 Replies)
Discussion started by: xavix
0 Replies

4. Solaris

Zone network issue

Hi guys, I got a global zone with with two zones runnig. After a patch upgrade (July 2010) one of them stop to working fine: basically I can't ping it ( I mean I can ping from the other zone, but actually the ping pass across the global zone..) and I can't access it in ssh or telnet...(actually... (0 Replies)
Discussion started by: cecco16
0 Replies

5. SuSE

XEN and SLES11

Good morning, Server:HP ProLiant DL165 G7 diskless with Disc on Storage OS:SLES11 SP1 and xen-3.3.1_18546_12-3.1 iSCSI:INTEL Gigabit ET Dual Port Server Adapter 825768 When I start SLES11 with Xen in boot-loader menu, then the boot will stop because linux could'nt find the iscsi interface... (0 Replies)
Discussion started by: hiddenshadow
0 Replies

6. Red Hat

VM network issue

Hi, I'm trying to create a lab environment in my personal laptop. I have created a virtualbox RHEL6.1 and I want to make another copy out of it to make it 4 instances by simply copying the whole folder and changing their name and then changing their IP addresses. is this OK? please advice. for... (2 Replies)
Discussion started by: messi777
2 Replies

7. Linux

Apache2-mpm-itk installation SLES11

Hi, do anyone know how to apply the corresponding apache2-mpm-itk patches to an already installed apache2 on a SLES11 machine? This is the link to the module: apache2-mpm-itk And this is the link to the patches: Index of /apache2.2-mpm-itk-2.2.17-01 Thanks (0 Replies)
Discussion started by: asanchez
0 Replies

8. Solaris

Network Printing issue

I have network printer registerd in solaris environment. When I issue print, it prints banner page. The issue printer is registerd in Print server which is running on Linux environment. So when I issue print in Print server, it doesn't print banner page as banner settings are made to turn off It... (6 Replies)
Discussion started by: Sunil Koya
6 Replies

9. Red Hat

Network Bonding Issue

I have one production system where my customized application runs.The applications require seamless network connectivity with different machines connected in LAN and WAN. As these applications are very critical, it is very much required to have a seamless network activity.The applications are... (4 Replies)
Discussion started by: Anjan Ganguly
4 Replies

10. Red Hat

Network issue in same vlan

We have two hosts in same vlan with same route rules. One of them is not able to connect to an outside IP while in another I get "failed: Connection timed out" while testing the connectivity through netcat. I have tried mtr /traceroute and it gives me the same results. Is there a netcat... (1 Reply)
Discussion started by: jacki
1 Replies
AUSCOPE(1)						      General Commands Manual							AUSCOPE(1)

NAME
auscope - Network Audio System Protocol Filter SYNOPSIS
auscope [ option ] ... DESCRIPTION
auscope is an audio protocol filter that can be used to view the network packets being sent between an audio application and an audio server. auscope is written in Perl, so you must have Perl installed on your machine in order to run auscope. If your Perl executable is not installed as /usr/local/bin/perl, you should modify the first line of the auscope script to reflect the Perl executable's location. Or, you can invoke auscope as perl auscope [ option ] ... assuming the Perl executable is in your path. To operate, auscope must know the port on which it should listen for audio clients, the name of the desktop machine on which the audio server is running and the port to use to connect to the audio server. Both the output port (server) and input port (client) are automati- cally biased by 8000. The output port defaults to 0 and the input port defaults to 1. ARGUMENTS
-i<input-port> Specify the port that auscope will use to take requests from clients. -o<output-port> Determines the port that auscope will use to connect to the audio server. -h<audio server name> Determines the desktop machine name that auscope will use to find the audio server. -v<print-level> Determines the level of printing which auscope will provide. The print-level can be 0 or 1. The larger numbers provide greater output detail. EXAMPLES
In the following example, mcxterm is the name of the desktop machine running the audio server, which is connected to the TCP/IP network host tcphost. auscope uses the desktop machine with the -h command line option, will listen for client requests on port 8001 and connect to the audio server on port 8000. Ports (file descriptors) on the network host are used to read and write the audio protocol. The audio client auplay will connect to the audio server via the TCP/IP network host tcphost and port 8001: auscope -i1 -o0 -hmcxterm auplay -audio tcp/tcphost:8001 dial.snd In the following example, the auscope verbosity is increased to 1, and the audio client autool will connect to the audio server via the network host tcphost, while displaying its graphical interface on another server labmcx: auscope -i1 -o0 -hmcxterm -v1 autool -audio tcp/tcphost:8001 -display labmcx:0.0 SEE ALSO
nas(1), perl(1) COPYRIGHT
Copyright 1994 Network Computing Devices, Inc. AUTHOR
Greg Renda, Network Computing Devices, Inc. 1.9.3 AUSCOPE(1)
All times are GMT -4. The time now is 01:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy