- This topic is empty.
-
Posts
-
I have installed WDM 4.8 on a Windows 2003 server, having followed the install guide download from the wyse website. I installed and configured IIS6 and FTP exactly as instructed.
I have created our subnet – 255.0.0.0 – and if I search for the V50L device on my desk nothing comes up. I originally thought the ridiculous subnet might be the problem but I can’t even add them manually by MAC address.
Strangely WDM finds the S10 device on my desk, but not the V10 on my colleagues desk.
Clearly I am doing something wrong. Can someone please tell me how I am supposed to configure the devices to see the server? I know this can be done using DHCP but I would prefer to do this manually for now.
APMali
Can you try to enter the IP address of the WDM server locally at you V50L and/or V10L? Do they checkin then?
HAgent is the WDM client tat resides on the units to communicate with the WDM server.
Depending on the OS you can either see this locally in the Addons (V50L) or remote via WDM. Just click on one unit and then on t “+” sign on the right bottom to get the full client info.CG
The IP address is correct, and actually I ended up configuring the “Wyse Device Manager” and “Wyse Device Manager Port” DHCP options to role it out. Strangely though, even though I entered port 21 on the DHCP server, all devices seem to pick up port 12594.
As it stands, any S10 device I plug in is picked up straight away by WDM. However, any V10 device, and more importantly (because we have dozens of them!) any V50L device does not show up. If I check Control Panel – Rapport Agent the IP address is correct and the port is the same as the S10 device (that strange 12594).
Regarding the hagent, the WDM 4.8 Installation guide tells me that certain hagents are not compatible with WDM 4.8 and that they must be upgraded. If I can’t connect to them in WDM how do I upgrade them on, for example, a V50L device? I have searched for an tech guide for doing this but I can only see info on how to update the Windows machines.
Thanks for your reply.
What are the names of your V10L units? Any “-” or “_” in the name? This would be a known issue and units will not check in.
Regarding the V50L. In the release notes I found a passage that mentions, that a V50L will not be discovered on a WDM 4.8 installed on W2k8 R2. But this is not the case for you.
I would recommend to
1. remove the DHCP option for WDM port and only keep OT 186
2. take a network trace of a V50L booting up. You may see any error messages in the WDM checkin.CG
Thanks. Does it make a difference that this is the free version downloaded from Wyse’s website? It is activated for 120 days or something like that.
The terminal name is still the default “derived from MAC address” and there are no hyphens or underscores. I removed the DHCP port option and rebooted the V50L terminal. In Control Panel – Rapport Agent the correct server is listed but now the port is 80.
I also did a network capture of the terminal booting up, this is what I saw:
(10.x.x.x is the server, 10.y.y.y is the client)No. Time Source Destination Protocol Info
44 51.108879 10.x.x.x 10.y.y.y TCP tr-rsrb-port > http [SYN] Seq=0 Win=5840 Len=0 MSS=1460 SACK_PERM=1 TSV=4294940095 TSER=0 WS=2No. Time Source Destination Protocol Info
45 51.108906 10.y.y.y 10.x.x.x TCP http > tr-rsrb-port [SYN, ACK] Seq=0 Ack=1 Win=16384 Len=0 MSS=1460 WS=0 TSV=0 TSER=0 SACK_PERM=1No. Time Source Destination Protocol Info
46 51.109114 10.x.x.x 10.y.y.y TCP tr-rsrb-port > http [ACK] Seq=1 Ack=1 Win=5840 Len=0 TSV=4294940096 TSER=0No. Time Source Destination Protocol Info
47 51.112305 10.x.x.x 10.y.y.y HTTP PUT /hserver.dll?&V01|&IMAC=008064606709|CID=0|CN=LWT008064606709|ED=1|IP=10.x.x.x|SM=255.0.0.0|GW=10.1.1.2|SN=10.255.255.255|1D=10.1.1.211|0D=1|AL=/usr/sbin/netxserv|AV=4.1.0.0|CP=VIA374Esther374processor374374800MHz|CPS=800|RM=190512|B1=1.18|PD2=1280x1024x16374@37460Hz|IM=6.6.2-02|CI=60|SN#=6KJ2G300033|OS=23|VI=1|P1=24|TZO=-421|TZ=PDT|FS=128|MD=2003-04|CO=|LO=|AP0=Base374System|NA|6.6.2-02|AP1=Rapport374Agent|NA|4.1.0-3.26|AP2=TrueType|NA|6.8.0-3.4|AP3=WebFonts|NA|2.0.4-3.6|AP4=TrueType374Fonts|NA|6.8.0-3.5|AP5=Network_login|NA|1.0.0-1.0.3|AP6=Screen374Saver|NA|3.13|AP7=DMonitor|NA|1.0.0-0.4.0|AP8=Mozilla374Firefox_15|NA|1.5.0.8-3.6|AP9=Remote374Shadow|NA|3.17|AP10=ICA374Client|NA|10.32-3.22.5|AP11=Remote374Desktop|NA|1.6.0-1.0|AP12=SNMP|NA|5.1.3.1-3.13|AP13=Linux374Printing|NA|3.8.27-3.33|AP14=SSH|NA|3.8.1-3.25|AP15=ThinPrint|NA|6.2.87-0.2|AP16=XDMCP|NA|6.8.0-3.29|AP17=Ericom|NA|8.2.0-3.29| HTTP/1.1No. Time Source Destination Protocol Info
49 51.205030 10.y.y.y 10.x.x.x HTTP Continuation or non-HTTP trafficNo. Time Source Destination Protocol Info
50 51.205231 10.y.y.y 10.x.x.x TCP http > tr-rsrb-port [FIN, ACK] Seq=34 Ack=1028 Win=64508 Len=0 TSV=8813 TSER=4294940095No. Time Source Destination Protocol Info
51 51.205243 10.x.x.x 10.y.y.y TCP tr-rsrb-port > http [ACK] Seq=1028 Ack=34 Win=5840 Len=0 TSV=4294940105 TSER=8813No. Time Source Destination Protocol Info
52 51.239343 10.x.x.x 10.y.y.y TCP tr-rsrb-port > http [ACK] Seq=1028 Ack=35 Win=5840 Len=0 TSV=4294940109 TSER=8813No. Time Source Destination Protocol Info
53 51.308738 10.x.x.x 10.y.y.y TCP tr-rsrb-port > http [FIN, ACK] Seq=1028 Ack=35 Win=5840 Len=0 TSV=4294940116 TSER=8813No. Time Source Destination Protocol Info
54 51.308765 10.y.y.y 10.x.x.x TCP http > tr-rsrb-port [ACK] Seq=35 Ack=1029 Win=64508 Len=0 TSV=8814 TSER=4294940116Can you post the content of the HTTP answering packages? Should be #49+
CG
Thanks, is this what you mean?
No. Time Source Destination Protocol Info
49 51.205030 10.1.1.232 10.1.1.123 HTTP Continuation or non-HTTP trafficFrame 49: 99 bytes on wire (792 bits), 99 bytes captured (792 bits)
Arrival Time: Oct 6, 2010 16:14:10.531787000 W. Australia Standard Time
Epoch Time: 1286352850.531787000 seconds
[Time delta from previous captured frame: 0.033475000 seconds]
[Time delta from previous displayed frame: 0.000000000 seconds]
[Time since reference or first frame: 51.205030000 seconds]
Frame Number: 49
Frame Length: 99 bytes (792 bits)
Capture Length: 99 bytes (792 bits)
[Frame is marked: False]
[Frame is ignored: False]
[Protocols in frame: eth:ip:tcp:http:data]
[Coloring Rule Name: Checksum Errors]
[Coloring Rule String: cdp.checksum_bad==1 || edp.checksum_bad==1 || ip.checksum_bad==1 || tcp.checksum_bad==1 || udp.checksum_bad==1 || mstp.checksum_bad==1]
Ethernet II, Src: 42:64:4f:26:66:6b (42:64:4f:26:66:6b), Dst: WyseTech_60:67:09 (00:80:64:60:67:09)
Destination: WyseTech_60:67:09 (00:80:64:60:67:09)
Address: WyseTech_60:67:09 (00:80:64:60:67:09)
…. …0 …. …. …. …. = IG bit: Individual address (unicast)
…. ..0. …. …. …. …. = LG bit: Globally unique address (factory default)
Source: 42:64:4f:26:66:6b (42:64:4f:26:66:6b)
Address: 42:64:4f:26:66:6b (42:64:4f:26:66:6b)
…. …0 …. …. …. …. = IG bit: Individual address (unicast)
…. ..1. …. …. …. …. = LG bit: Locally administered address (this is NOT the factory default)
Type: IP (0x0800)
Internet Protocol, Src: 10.1.1.232 (10.1.1.232), Dst: 10.1.1.123 (10.1.1.123)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 85
Identification: 0x07cf (1999)
Flags: 0x02 (Don’t Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (6)
Header checksum: 0x0000 [incorrect, should be 0xdb6f]
Source: 10.1.1.232 (10.1.1.232)
Destination: 10.1.1.123 (10.1.1.123)
Transmission Control Protocol, Src Port: http (80), Dst Port: tr-rsrb-port (1996), Seq: 1, Ack: 1028, Len: 33
Source port: http (80)
Destination port: tr-rsrb-port (1996)
[Stream index: 1]
Sequence number: 1 (relative sequence number)
[Next sequence number: 34 (relative sequence number)]
Acknowledgement number: 1028 (relative ack number)
Header length: 32 bytes
Flags: 0x18 (PSH, ACK)
Window size: 64508
Checksum: 0x17ac [validation disabled]
Options: (12 bytes)
NOP
NOP
Timestamps: TSval 8813, TSecr 4294940095
[SEQ/ACK analysis]
Hypertext Transfer Protocol
Data (33 bytes)0000 26 45 52 7c 41 67 65 6e 74 20 4e 6f 74 20 53 65 &ER|Agent Not Se
0010 6e 64 69 6e 67 20 76 61 6c 69 64 20 76 61 6c 75 nding valid valu
0020 65 e
Data: 2645527c4167656e74204e6f742053656e64696e67207661…
[Length: 33]Just to let everyone who may be pulling their hair out know that Wyse have acknowledged a bug with WDM 4.8 and are looking to fix it. They were able to replicate the same error as me.
Confgen cheers for your help
apmali
apmali,
Do you know if they have created a patch for the v50L’s? I’m having the same issue and would love to get this resolved!
Thank you,
AWhi everyone,
same problem here with C10LE & V10L (no dash or underscore)
does anyone got a solution from Wyse
between WDM 4.8 and Firmware 7, Wyse is quite buggy these days / months
thank you
- You must be logged in to reply to this topic.