SAP router connection is not working
Dear Experts,
I cannot connect my systems to SAP, getting the below error.My router is not expired and port 3299 is reachable.
SAPRouter "dev_rout" log as follows:
trc file: "dev_rout", trc level: 1, release: "720"
Wed Apr 09 15:55:51 2014
SAP Network Interface Router, Version 40.4
command line arg 0: C:\saprouter\saprouter.exe
command line arg 1: -r
command line arg 2: -W
command line arg 3: 60000
command line arg 4: -R
command line arg 5: C:\saprouter\saprouttab
command line arg 6: -K
command line arg 7: p: CN=SOLMAR, OU=0000881026, OU=SAProuter, O=SAP, C=DE
SncInit(): Initializing Secure Network Communication (SNC)
PC with Windows NT (mt,ascii,SAP_UC/size_t/void* = 8/64/64)
GetUserName()="Administrator" NetWkstaUser="Administrator"
SncInit(): Trying environment variable SNC_LIB as a
gssapi library name: "C:\saprouter\nt-x86_64\sapcrypto.dll".
File "C:\saprouter\nt-x86_64\sapcrypto.dll" dynamically loaded as GSS-API v2 library.
SECUDIR="C:\saprouter\" (from $SECUDIR)
The internal Adapter for the loaded GSS-API mechanism identifies as:
Internal SNC-Adapter (Rev 1.0) to SAPCRYPTOLIB
Product Version = SAPCRYPTOLIB 5.5.5C pl36 (Jul 3 2013) MT,[aesni],NB
main: pid = 3656, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)
reading routtab: 'C:\saprouter\saprouttab'
Wed Apr 09 16:00:49 2014
NiHLGetHostName: to get 192.168.4.69 succeeded in 4660ms (tl=2000ms)
Wed Apr 09 16:00:50 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:12 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:13 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:24 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:25 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:27 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:08:16 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:11:42 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:10 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:11 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:12 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:04 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:55:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 06:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 06:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:37 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:38 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:39 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:58:15 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
SAPRoutab:
P * * *
P 192.168.0.96 194.117.106.129 3299
P 192.168.0.96 194.117.106.129 *
# SNC-connection from and to SAP
#KT "p:CN=sapserv1, OU=SAProuter, O=SAP, C=DE" 194.117.106.129 *
# SNC-connection from SAP to local R/3-System for Support
#KP "p:CN=sapserv1, OU=SAProuter, O=SAP, C=DE" 192.168.* 32*
P * 194.117.106.129 *
P 127.0.0.1 194.117.106.129 3299
P * * *
P sapserv1 192.168.0.165 3389
P sapserv1 192.168.0.96 3389
P sapserv1 192.168.0.162 3389
SAPOSS Screens:
Hi Philip
This looks fine. Just click on change and save again , it will automatically create SAPOSS RFC, u can see that in TX; SM59,
seems you Public IP : 192.168.0.96
The entry that you maintained in the sapsouttab was:
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.0.96, 3200
you supposed to maintain the IP Address of the server that you opening the connection.not the router IP(192.168.0.96,)
make sure it looks like the below:
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <IP Address of the server that you working with RFC>, 3200
Please follow this:
1.Maintain then correct entries in the saprouttab
2.restart the saprouter
3.Delete RFC: SAPOSS from TX:SM59
4. Recreate the RFC: SAPOSS from OSS1 after deleting that from SM59..
5.Go to TX: SM59 and open the RFC:SAPOSS and go to technical setting tab: and make sure that the string looks ok and make sence(if requied copy the string frm the anotherserver where the RFC:SAPOSS is workingalready) and go to log on security tab and reenter the password of the user:OSS_RFC as CPIC (all in Capital letters)
save it and test.
please send me the screen shots of saproutab and screen shot of the SAPOSS RFC from SM59 and error screen shot.
hope it clarifies the now.
Kind Regards,
Phaneendra kakani
Similar Messages
-
you must have connected the Time Capsule with a router that does not work with my direct cable from my ISP
I tried to answer in your other post.. please stick to one thread ..
What method of internet do you have.. is this fibre install.. if so the TC should just plug in and use dhcp in router mode.. press and hold the reset and it will go back to router mode by default. -
since the last update to iTunes 11.0.3 (42) the airplay connection is not working properly , keeping breaking up, while the airplay works fine with my iPad and iPhone. Anyone has experienced the same? any fix available?
Hi Erdelestre,
Thanks for visiting Apple Support Communities!
See this article for some tips about troubleshooting AirPlay:
Troubleshooting AirPlay and AirPlay Mirroring
http://support.apple.com/kb/ts4215
Troubleshooting performance issues with AirPlay or AirPlay Mirroring
If you are experiencing intermittent playback or significant network lag with AirPlay or AirPlay Mirroring, it could be due to a weak Wi-Fi connection, interference, or the distance between the Wi-Fi router and your iOS device, Apple TV or AirPort Express. Try the following suggestions:
Ensure that other devices are not trying to stream to the same Apple TV at the same time.
Turn off Bluetooth on your iOS device by tapping Settings > General > Bluetooth.
Ensure that your Wi-Fi router is set up with the recommended settings for the best performance.
Certain external devices, such as microwave ovens and baby monitors, may interfere with a Wi-Fi network. Try moving or disabling these devices.
If possible, try to locate your Wi-Fi router in the same room as your Apple TV and iPhone/iPad.
If your wireless and wired networks are the same, try connecting your Apple TV to the router via Ethernet instead of Wi-Fi.
If the Wi-Fi router has an external antenna, check to see that is it connected properly and in good condition.
Use the Wi-Fi network troubleshooting guide to resolve interference and other issues.
Best,
Jeremy -
Bug (?) with Corporate Connectivity is (not) Working check
Noticed something odd. In situations where:
Direct Access client is offsite
their Internet access is via WiFi
they first have to enter their access credentials through a web-based captive portal before access is granted
then the Corporate Connectivity Check process malfunctions. Have seen cases where, after accessing the captive portal and being authenticated, Internet access works on the client. Direct Access then connects successfully. This is confirmed
on the server console, showing the client connected and the user credentials used. The client is able to access internal resources just fine (e.g. network drives on file servers).
But on the client itself, it still says Corporate Connectivity is Not Working. The WiFi icon is showing an exclamation mark. My belief is that this is caused by the client's inability to access Microsoft NCSI servers in a timely fashion.
So it looks like the corporate connectivity checks are dependent on Microsoft NCSI checks.
Can someone at Microsoft please look into this, as it is confusing our users (not to mention us guys in IT who have only just discovered this odd behaviour!).Hi Steven !
Thanks a lot for your guidance !
After I followed the steps, I found that the time out occurs when trying to resolve the internal domain name.
The Windows Firewall was enabled on all profiles ( active on the public )
There were no IPsec sessions established in the Security associations tab, so I enabled the audit policy of the IPsec as per your instructions.
There is reoccurring error in the Security log :
Date: 10/8/2014 10:08:49 AM
Event ID: 4653
Task Category: IPsec Main Mode
Level: Information
Keywords: Audit Failure
User: N/A
Computer: MyW8Client
Description:
An IPsec main mode negotiation failed.
Local Endpoint:
Local Principal Name: -
Network Address: MyW8Client_Ipv6 address
Keying Module Port: 500
Remote Endpoint:
Principal Name: -
Network Address: MY_DA_Servert Ipv6 address
Keying Module Port: 500
Additional Information:
Keying Module Name: AuthIP
Authentication Method: Unknown authentication
Role: Initiator
Impersonation State: Not enabled
Main Mode Filter ID: 180987
Failure Information:
Failure Point: Local computer
Failure Reason: Negotiation timed out
State: Sent first (SA) payload
Initiator Cookie: 9e636863e513b367
Responder Cookie: 0000000000000000
As far as I understand - the connection can not be established due to certificate error, which in my case is strange since my DA configuration is set to not use computer certificates, only Kerberos.
I will keep digging but any additional tip/advice will be appreciated!
Thanks again, Steven!
P.S. Just noticed that the Event ID 4653 produce two types of "Failure Reason" - apart from "Negotiation timed out" I also get "No policy configured" -
My 3G connection is not working after updating to iOS 6.1. I have tried all possible solutions like resetting the network , restarting iPad , ...
The same story. No 3G after updating to 6.1. Told my daughter temporarily not to do an update on her iPad with 6.01. We've exchanged SIMs. I inserted her SIM in my iPad - 3G appeared immediately. And my SIM in her iPad with ios 6.01 also WORKS FINE. We use the same provider - Megafon Moscow. After attempting to revert SIMs to original configuration, 3G disappeared on my iPad again. Don't know what's going on with SIM during the update to 6.1
-
why does iTunes keep giving me bogus error messages. "Your internet connection is not working, check your connection and try again." My internet is working fine. iTunes is not working and will not allow me to download tunes.
This my sound too simple, but I just kept clikning on the arrow next to the selected music and it finally "Kicked" in.
I live in Europe ,So Be persistent and don't give up ! Aug. 2013 -
I ipod classic 80 gb when I am connected pc connected after that is hanged just showing connected its not working any button .
Try connecting it to another PC, if it is ok, then your PC has some software conflict with iTunes.
If it hangs other PC also, then your iPod Hardisk, maybe bad.
Do the disk diagnosticas posted earlier by tt2, to check the health of your Hardisk.
Have a nice day! -
Why does my camera connection kit not work with my ipad 1 after updating on ios 5?
Why does my camera connection kit not work with my ipad 1 after updating on ios 5? What can I do to make it work again?
It should. It will only respond if there's something on the card for it to respond to, so do you have pics on the card?
And if it's messing up; try giving the iPad a restart. Hold down the sleep and home keys, past when you see hte red power down slider and until you see the silver apple. Let it reboot and try again. That can clear up any glitches on the device itself. -
Internet connection does not work when Macbook wakes up from sleep
I recently installed MAC OSX LION. After that whenever the macbook pro wakes up from sleep, the internet connection does not work. I get a message 'DNS lookup failed'. I have to Turn off the WIFI and turn it back on every time. Has anyone come across this?
Same problem here. But I am afraid it has nothing to do with Safari because I don't even have Safari open. When it wakes from sleep, it has no internet connection and i cannot get me mail unless I shut wifi off and then back on. This happened back at the start of Snow Leopard too and it was something Apple eventually fixed.
-
SAP FTP Binary Does not work after EHP 7 Upgrade
Hi All,
Since EHP 7, if I try to execute an external command through sm49, which has a shell script for ftp connection and fetching files, the 'binary' command after ftp connection is not working.
Result? I'm fetching corrupted files once in a while. The same was fine before the upgrade. The script runs fine at OS level. We are using AIX.
Did anyone see this issue before? Is there a solution?
Please help, it's quite urgent.
Thank you.
UdayHi Uday,
Since EHP 7, if I try to execute an external command through sm49, which has a shell script for ftp connection and fetching files, the 'binary' command after ftp connection is not working.
1) What is the exact error message you get ?
2) Did you check permission to the script . Ensure sidadm has full access to execute it.
3) Did you check Test Connection to TCP/IP RFC destinations SAPFTP and SAPFTPA are working fine in SM59 ?
Regards,
Deepak Kori -
My database connectivity is not working inspite of installing sql express
My database connectivity is not working inspite of installing sql express ...what should I do so that my database works
Hello karan7,
In addition to pvdg's post, can you reproduce this issue with a new fresh database? If you can this means it is a SQL Setup related problem. If you cannot, your database file may already corrupt.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Hello,
on several Windows 7 Clients the update/refresh of the RemoteApp and Desktop Connections stopped not working automatically. There is a Update failed error. When we do an "Update Now" manually, it gets synchronized without problems.
I am asking me if there is an issue with a stored Password as we Need to Change the Passwords regularily. The error is occuring for Connections to all RDS Servers (we have severals).
Does Windows store the user Password in the Task Scheduler? If yes, does the schedule Task Password Change automatically after the Domain Password Change?
Or what else could be the issue? The RDS Server and the certificate (Name the same as the URL) seems to be fine as not all Clients have this issue.
Thank you for your helpHi,
Thank you for posting in Windows Server Forum.
By default it will automatically update the RemoteApp and Desktop Connections but if in any particular case it’s not happening then for a try you can restart the server and check the result again. In addition you can try running below command and check
the result.
Start-Process rundll32 -ArgumentList "tsworkspace,TaskUpdateWorkspaces2
More information:
Powershell to update "RemoteApp and Desktop Connections"
If a task is registered using the Administrators group for the security context of the task, then you must also make sure the Run with highest privileges check box is checked if you want to run the task. Please check “Task
Security Context” for more details.
Hope it helps!
Thanks,
Dharmesh -
HP Pavilion Entertainment PC: WiFi works, however, hard wired connection does not work.
Internet via WiFi works, however, hard wired connection does not work.
My software indicates my hardware is working properly.
However, if I connect another computer to the cable I am using, it connects to the internet without a problem.
And, if I connect my comupter to another cable that works with another computer, my computer still does not connect to the internet.
HP Pavilion dv9700 Notebook PC
32-bit Operating System
Windows Vista Home Premium Service Pack 2It could be that the touch pad is broken on the inside and the contact area for the one button is either broken, blocked with an object or the cable going to the mother board is not inserted correctly into the mother board connector. I think in any case the case will have to come off and someone look for physical/connection problems. It doesn't sound like a software problem but there is always a chance.
Reminder: Please select the "Accept as Solution" button on the post that best answers your question. Also, you may click on the white star in the "Kudos" button for any helpful post to give that person a quick thanks. These feedback tools help keep our community active, so you receive better answers faster. -
SMO Connection Manager Not Working
I'm using SSDT 2012 to create SMO Connection Manager for transferring server objects. However the connection is not working, it always returns error message something like "server is not found". I tried to connect multiple servers, with both
Windows and SQL authentications, none of them works. I found the SMO.dll is already installed in the specific folder on my development machine. What would be the reason of this error? Thanks.
-------Edited----------------------------------------------------
Added the error message below. I can connect the server using OLEDB or ADO.NET. So my question is, is there a service, protocol or port .... to get SMO Server ready for responding?I see you used to connect to the local machine with the "." notation.
In this case shared memory is used, thus make sure this option is allowed.
I'd try connecting using the IP or the full name.
Arthur My Blog -
Hi, not network, not connected hard, not work wi-fi or other name? i dont know
hi, not network, not connected hard, not work wi-fi or other name? i dont know, please what name other network?
Thank you!Check your system for possible Malware. But you have to do it in WIndows Safe Mode.
(Do not use your own Anti-virus to SCAN)
Start your computer in "Safe mode with networking", go to this link download a free version of Malwarebyte.
http://www.malwarebytes.org/products/malwarebytes_free
Install and perform update immediately, then do a full SCAN. Remove malware if it indeed finds any. Restart computer to regular windows to let Malwarebyte complete the removal.
To start your computer in safe mode
Press and hold the F8 key as your computer starts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you'll need to try again by waiting until the Windows logon prompt appears, and then shutting down and restarting your computer.
On the Advanced Boot Options screen, use the arrow keys to highlight the "safe mode with networking" option, and then press Enter. Log on to your computer with a user account that has administrator rights.
When your computer is in safe mode, you'll see the words Safe Mode in the corners of your screen. To exit safe mode, restart your computer and let Windows start normally.
Maybe you are looking for
-
Jabber for Windows 9.2.0 on VXC
I've upgraded to 9.2.0 Jabber for Windows. I was previously on Beta drop 2. Since upgrading to 9.2.0 I've lost all video capability. I've tried this with the Tandberg Precision HD bullet cam and the Logitech C920-C. I am running VXC image 8.7 voice v
-
i didnt have issues with itunes before...but pc asked to download new version. i did. when i click itunes i get my original music, but when i click store...i get nothing. i watched tutorial....but still cant open itunes store. im looking for music to
-
When creating a subcontracting Purchase Order is is possible to issue components separate from the goods receipt. Our current SAP system configuration requires the user to receive some amount of the material being manufactured by the subcontractor an
-
[Solved] How to resize an encrypted luks partition?
Edit: This worked: http://www.enigmacurry.com/2007/04/28/r - ilesystem/ I have some empty space on my harddrive, and wish to fill it up, with my existing partition. This is my harddrive setup in gparted: And fdisk respectively: [ricky@archlinux ~]$ s
-
Hi, How can i tune I/O? Kindly, anyone can explain I/O tuning step wise.