06-11-2015
10 More Discussions You Might Find Interesting
1. IP Networking
Hi
I have my DNS servers (BIND 8) running on two Solaris 8 boxes. I need to be able to resolve an address blah.xxx.net to an IP address followed by :8080 - (for Tomcat). I tried doing this in my zone file but it failed. Can someone give me a pointer on where this configuration should be done?... (1 Reply)
Discussion started by: korfnz
1 Replies
2. UNIX for Dummies Questions & Answers
hey everyone,
i have just finished configuring apache 2.0 with the php and pgsql modules installed on it.. httpd.conf is configured and everything is running right after a lengthy bit of reading and struggling with the system.. the only problem left is how do i enable the port that i would access... (3 Replies)
Discussion started by: moxxx68
3 Replies
3. AIX
HI all,
Ping is happening to a AIX box...but telnet is not happening...
AIX box doesn't have any conslole...
Please help how to resolve it.
Thanks in advance ..
Manu (2 Replies)
Discussion started by: b_manu78
2 Replies
4. AIX
Hi All,
We are not able to ping to a AIX box...Network is ok..when we give ping from that AIX box..it is giving 0821-067 ping: The socket creation call failed.there is no enough buffer space for the requested socket operation.
refresh -s inetd is also giving socket error.
Please help to... (1 Reply)
Discussion started by: b_manu78
1 Replies
5. Solaris
we disabled telnet on solaris 9 via previous a thread. We use CMS (call management system) supervisor which used port 23 (telnet). We cannot use telnet via local directive and it was shut down as stated when we shut down telnet in the inetd file. I cannot now log into the CMS box since port 23 is... (3 Replies)
Discussion started by: panzerkw
3 Replies
6. AIX
Hi All,
I would like to monitor the volume of Data that is transferred through a single port in AIX. I have nmon installed in my machine. What is the best possible solution for this problem.
Thanks in Advance. (3 Replies)
Discussion started by: bravo13
3 Replies
7. IP Networking
Hi,
I am trying to set up a dev environment and I have Ubuntu server (10.16.1.92) and a CentOS VM (10.16.3.235) on this. On the CentOS I have a program running on port 5433. Now my problem is that I am unable to telnet this port from another Windows server whereas I can telnet port 22 from... (5 Replies)
Discussion started by: rishav
5 Replies
8. UNIX for Dummies Questions & Answers
Hi,
Well this is probably a silly one that I should know...but I don't !
I'm telnetting to various ports from a shell script and the telnet is echoing back that it's 'trying xxx.xx.xx.xx...' but not the port number it's trying!
Any help much appreciated
Thanks (1 Reply)
Discussion started by: Grueben
1 Replies
9. Red Hat
Hi Experts,
I am receiving below error while trying to connect port 8080.
Could not open connection to the host, on port 8080 : connection refused.
iptables configuration
/etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of... (1 Reply)
Discussion started by: sai_2507
1 Replies
10. Solaris
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
LEARN ABOUT HPUX
gss_verify_mic
gss_verify_mic(3) Library Functions Manual gss_verify_mic(3)
NAME
gss_verify_mic() - check a cryptographic message integrity code (MIC) against a message to verify its integrity
SYNOPSIS
DESCRIPTION
The routine verifies that a cryptographic MIC, contained in the token_buffer parameter, fits the supplied message. The application receiv-
ing the message can use the qop_state parameter to check the strength of protection.
Input Parameters
context_handle Specifies the context on which the message arrived.
message_buffer Specifies the message to be verified.
token_buffer Specifies the token to be associated with the message.
Output Parameters
qop_state Returns the quality of protection gained from message integrity code (MIC). Specify NULL if not required.
minor_status Returns a status code from the security mechanism.
STATUS CODES
The following status codes can be returned:
The routine was completed successfully.
The token failed consistency checks.
The MIC was incorrect.
The token was valid, and contained a correct
MIC for the message, but it had already been processed.
The token was valid, and contained a correct
MIC for the message, but it is too old.
The token was valid, and contained a correct MIC
for the message, but has been verified out of sequence. A later token has already been received.
The token was valid, and contained a correct MIC
for the message, but has been verified out of sequence. An earlier expected token has not yet been received.
The context has already expired.
The routine failed. Check the
minor_status parameter for details.
The context identified in the
context_handle parameter was not valid.
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
gss_get_mic(3), gss_wrap(3).
The manpages for DCE-GSSAPI are included with the DCE-CoreTools product. To see those manpages add to
gss_verify_mic(3)