Author Topic: nc.windows.app.23704 error again  (Read 7356 times)

redeyes_f

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
nc.windows.app.23704 error again
« on: July 17, 2007, 04:09:22 am »
Hi all,

 I've a problem using NC 5.5.0 both with IE7.0 and FF2.0.

 During connection negotiation appears this error window. Searched trough this forum but found anything useful about this topic.

 Checking diagnostic, i found this:
 "DebugId" '' [Debug] : *****: . . . Juniper Network Connect Virtual Adapter Enabled
2007/07/17 11:14:48.171 dsNcDiag: t1304 "DebugId" '' [Debug] : *****: . . . . . . IP Address: 10.8.8.1
2007/07/17 11:14:48.171 dsNcDiag: t1304 "DebugId" '' [Debug] : *****: . . . . . . Subnet Mask: 255.255.255.255
2007/07/17 11:14:48.171 dsNcDiag: t1304 "DebugId" '' [Debug] : *****: . . . . . . Default Gateway:  Ping Skipped, Invalid Address
2007/07/17 11:14:48.171 dsNcDiag: t1304 "DebugId" '' [Debug] : *****: . . . . . . DHCP Server: 10.200.200.200 Ping Failed
2007/07/17 11:14:48.171 dsNcDiag: t1304 "DebugId" '' [Debug] : *****: . . . . . . Primary WINS Server: 10.8.6.204 Ping Failed
2007/07/17 11:14:48.171 dsNcDiag: t1304 "DebugId" '' [Debug] : *****: . . . . . . Secondary WINS Server: 0.0.0.0 Ping Skipped, Invalid Address
2007/07/17 11:14:48.171 dsNcDiag: t1304 "DebugId" '' [Debug] : *****: . . . . . . DNS Server: 10.8.6.202 Ping Failed
2007/07/17 11:14:48.171 dsNcDiag: t1304 "DebugId" '' [Debug] : *****: . . . . . . . . . . . . 10.8.6.203 Ping Failed

 But network adapter seems ok (result of ipconfig/all:)
Scheda Ethernet Network Connect Adapter:
   Suffisso DNS specifico per connessione:
   Descrizione . . . . . . . . . . . . . : Juniper Network Connect Virtual Adapter
   Indirizzo fisico. . . . . . . . . . . : 00-FF-68-CD-8E-85
   DHCP abilitato. . . . . . . . . . . . : Sė
   Configurazione automatica abilitata   : Sė
   Indirizzo IP. . . . . . . . . . . . . : 10.8.8.1
   Subnet mask . . . . . . . . . . . . . : 255.255.255.255
   Gateway predefinito . . . . . . . . . :
   Server DHCP . . . . . . . . . . . . . : 10.200.200.200
   Server DNS . . . . . . . . . . . . .  : 10.8.6.202
                                       10.8.6.203
   Server WINS primario . . . . . . . .  : 10.8.6.204
   Lease ottenuto. . . . . . . . . . . . : martedė 17 luglio 2007 10.11.35
   Scadenza lease . . . . . . . . . . .  : martedė 24 luglio 2007 10.11.35

And in ncservice.log appears these errors:
ervice: t194 "DebugId" 'NCSys' [Debug] NCSys: Juniper Network Connect Virtual Adapter MTU = 1200
2007/07/17 11:07:02.093 dsNcService: t194 "DebugId" 'adapter' [Debug] adapter: Calculated MTUs differ, IVE(1400) Client (1200)
2007/07/17 11:07:02.093 dsNcService: t194 "DebugId" 'NCSys' [Debug] NCSys: No change to identical MTU 1200.
2007/07/17 11:07:02.093 dsNcService: t194 "DebugId" 'adapter' [Debug] adapter: Set 2 DNS server
2007/07/17 11:07:32.187 dsNcService: t194 "DebugId" 'adapter' [Debug] adapter: Failed to configure adapter after 30 tries
2007/07/17 11:07:32.187 dsNcService: t194 "DebugId" 'session' [Debug] session: Error in handling config!
2007/07/17 11:07:32.187 dsNcService: t194 "DebugId" 'session' [Debug] session: disconnecting from ive XXXXXXXXX with reason 4
2007/07/17 11:07:32.187 dsNcService: t194 "DebugId" 'adapter' [Debug] adapter: closing tun adapter 00000D78
2007/07/17 11:07:32.187 dsNcService: t194 "DebugId" 'adapter' [Debug] adapter: unregistering the adapter IO handler

Any idea about what problem can be and what means bold part?

On this server I had hamachi too (now uninstalled) and a virtual server 2003 working. Can be some problem with other virtual nics?

Tnx in advance



frent16

  • Newbie
  • *
  • Posts: 38
  • Karma: +0/-0
    • View Profile
Re: nc.windows.app.23704 error again
« Reply #1 on: July 17, 2007, 08:37:38 am »
The disconnect with reason 4 message basically means that there was an issue when trying to configure the Network Connect virtual adapter on the machine, as the line before the disconnect states: Error in handling config!  I have seen these same errors before when there is an incorrect subnet defined in split tunneling policies, and generally means that there is an issue with the configuration on the IVE.  Is there more than one person having the issue?  If everyone is having the issue then it is likely an issue with the config, if it is only this machine that the logs are from then I would say that it is an issue with the other virtual adapters that are installed.

redeyes_f

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: nc.windows.app.23704 error again
« Reply #2 on: July 19, 2007, 04:21:58 am »
For other people it works. I saw errors about adapter in log, and i disabled other virtual adapters (Hamachi) but without any effect. Perhaps problem is in Virtual Server 2005 that runs on that machine... i tried to stop it but problem is still there... any known issues between NC and Virtual server 2005?

frent16

  • Newbie
  • *
  • Posts: 38
  • Karma: +0/-0
    • View Profile
Re: nc.windows.app.23704 error again
« Reply #3 on: July 19, 2007, 09:14:18 am »
I'm not aware of any issues between NC and Virtual Server 2003 (I think you meant 2003, not 2005?).  Looking at the logs again, when ipconfig /all was run, and the adapter seemed to be OK, the default gateway was never defined; also in the diagnostic, the ping was skipped because it was an invalid address.  What OS is NC running from?  You may need to uninstall the other virtual adapters/software and try the connection again to get it to work correctly; I have seen where uninstalling both the NC client, and other VPN adapters then installing NC has worked.  Most times, if NC is installed first there aren't any issues.

redeyes_f

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: nc.windows.app.23704 error again
« Reply #4 on: July 20, 2007, 08:56:05 am »
NC runs on a W2003 SBS that works as DC of a test domain with only one workstation joined. On that server there was Hamachi, but I already unistall it and reinstalled NC after hamachi uninst and reboot, but with no effect. There is no other virtual adapter installed, but errors are the same in all cases.

CrazyBird

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: nc.windows.app.23704 error again
« Reply #5 on: January 27, 2008, 12:01:11 pm »
Hello!

I also have the same problem with Network Connect 5.5.0:

2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=1
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=2
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=3
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=4
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=5
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=6
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=7
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=8
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=9
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=10
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=11
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=12
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=13
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=14
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=15
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Not RR NIC , i=16
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Found RR NIC {FCBB7E5D-7669-4576-AB14-208CDE2B00CA}, i=17
2008/01/27 17:52:39.674 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Can't find NC in binding
2008/01/27 17:52:42.298 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: starting dns...
2008/01/27 17:52:42.298 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Wait 250ms when starting dns..., status: 2000
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Dns started in 250ms.
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'session' [Debug] session: IVE sent WINS server 255.255.255.255
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'session' [Debug] session: IVE sent NC IP 172.23.31.47
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'adapter' [Debug] adapter: IVE MTU is not received
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'adapter' [Debug] adapter: IVE get DNS server 129.221.130.10
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'adapter' [Debug] adapter: IVE get DNS server 129.221.133.22
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Dell Wireless 1450 Dual Band WLAN Mini-PCI Karte - Packet Scheduler Miniport MTU = 1500
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: Broadcom NetXtreme 57xx Gigabit Controller - Packet Scheduler Miniport MTU = 1500
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'adapter' [Debug] adapter: IVE and Client MTU values are same : 1400
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: No change to identical MTU 1400.
2008/01/27 17:52:42.548 dsNcService: tDC  "DebugId" 'adapter' [Debug] adapter: Set 2 DNS server
2008/01/27 17:53:12.792 dsNcService: tDC  "DebugId" 'adapter' [Debug] adapter: Failed to configure adapter after 30 tries
2008/01/27 17:53:12.792 dsNcService: tDC  "DebugId" 'session' [Debug] session: Error in handling config!
2008/01/27 17:53:12.792 dsNcService: tDC  "DebugId" 'session' [Debug] session: disconnecting from ive mks01.spt.unisys.com with reason 4
2008/01/27 17:53:12.792 dsNcService: tDC  "DebugId" 'adapter' [Debug] adapter: closing tun adapter 00000374
2008/01/27 17:53:12.792 dsNcService: tDC  "DebugId" 'adapter' [Debug] adapter: unregistering the adapter IO handler
2008/01/27 17:53:13.974 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: SetState: state: 0
2008/01/27 17:54:07.681 dsNcService: tDC  "DebugId" 'NCSys' [Debug] NCSys: SetState: state: 1
2008/01/27 17:54:10.074 dsNcService: tDC  "DebugId" 'adapter' [Debug] adapter: adapter not down.

I have a Dell Latitude D610 notebook and we are using Symantec Protection Agent 5.1.

I do not have any virtual network adapters left (there has been a vmware worksation installed) and also tried to deactivate the protection agent but the problem didn't disappear.