HP Xw460c Remote Graphics Software 4.2.0 User Guide - Page 147

The Remote Graphics Software Sender has refused

Get HP Xw460c - ProLiant - Blade Workstation PDF manuals and user guides View all HP Xw460c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 147 highlights

Authentication failed! Troubleshooting ping IP address If no ping reply is received, the Sender is unreachable or is not running. If a ping reply is received, the Sender software may not be running on the remote computer. 2. A Sender is not running on the system you are attempting to reach. Verify that the Sender is running on the system. 3. The Sender system is not started or connected to the network. You could try a basic connectivity test, such as ping. 4. The network is not configured correctly. For example, DNS may not have resolved the name of the Sender system correctly or your /etc/hosts file, if using UNIX, does not have the proper ipaddress mapped to the hostname. Try entering the ipaddress of the Sender. 5. The Sender is started and listening on a different network interface than the one you are attempting to reach. This could be the case if the Sender system has multiple NICs, it is a multihomed system, or there is a virtual ethernet device installed. If this is true you may need to specify the binding order of hostnames to ipaddress. 6. If you are attempting to connect to a UNIX system you may have entered an incorrect screen number. 7. If the Sender system has changed networks and been assigned a new ipaddress after the Sender was started then you'll need to re-start the Sender service/daemon. The Remote Graphics Software Sender has refused to allow a connection. Possible reasons include the following: 1. The authentication credentials that you entered, such as domain name, user name and password, are not valid or recognized by the Sender system. 2. The Sender's authentication is not configured appropriately. Please consult the User's manual and README.txt for the latest directions and issues with respect to configuring authentication. 139

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
Troubleshooting
139
ping
IP address
If no ping reply is received,
the Sender is
unreachable or is not running.
If a ping reply is received,
the Sender software
may not be running on the remote computer.
2.
A Sender is not running on the system you are
attempting to reach. Verify that the Sender is
running on the system.
3.
The Sender system is not started or connected to
the network. You could try a basic connectivity
test, such as ping.
4.
The network is not configured correctly. For
example, DNS may not have resolved the name
of the Sender system correctly or your /etc/hosts
file, if using UNIX, does not have the proper
ipaddress mapped to the hostname. Try entering
the ipaddress of the Sender.
5.
The Sender is started and listening on a different
network interface than the one you are
attempting to reach. This could be the case if the
Sender system has multiple NICs, it is a multi-
homed system, or there is a virtual ethernet
device installed. If this is true you may need to
specify the binding order of hostnames to
ipaddress.
6.
If you are attempting to connect to a UNIX
system you may have entered an incorrect
screen number.
7.
If the Sender system has changed networks and
been assigned a new ipaddress after the Sender
was started then you'll need to re-start the
Sender service/daemon.
Authentication
failed!
The Remote Graphics Software Sender has refused to
allow a connection. Possible reasons include the
following:
1.
The authentication credentials that you
entered, such as domain name, user name
and password, are not valid or recognized by
the Sender system.
2.
The Sender's authentication is not configured
appropriately. Please consult the User's
manual and README.txt for the latest
directions and issues with respect to
configuring authentication.