RailPro > RailPro Specific Help & Discussion
Can’t connect to Ring Servers
KB02:
pktmon start [--capture [--counters-only] [--comp <selector>] [--type <type>]
[--pkt-size <bytes>] [--flags <mask>]]
[--trace --provider <name> [--keywords <k>] [--level <n>] ...]
[--file-name <name>] [--file-size <size>] [--log-mode <mode>]
Start packet capture and event collection.
Packet Capture
-c, --capture
Enable packet capture and packet counters.
-o, --counters-only
Collect packet counters only. No packet logging.
--comp { all | nics | id1 id2 ... }
Select components to capture packets on. Can be ALL components,
NICs only, or a list of component Ids. Default is ALL.
--type { all | flow | drop }
Select which packets to capture. Default is ALL.
--pkt-size <bytes>
Number of bytes to log from each packet. To always log the entire
packet set this to 0. Default is 128 bytes.
--flags <mask>
Hexadecimal bitmask that controls information logged during packet
capture. Default is 0x012.
0x001 - Internal Packet Monitor errors.
0x002 - Information about components, counters and filters.
0x004 - NET_BUFFER_LIST group source and destination information.
0x008 - Select packet metadata from NDIS_NET_BUFFER_LIST_INFO.
0x010 - Raw packet, truncated to the size from --pkt-size.
Event Providers
-t, --trace
Enable event collection.
-p, --provider <name>
Event provider name or GUID. For multiple providers, use this
parameter more than once.
-k, --keywords <k>
Hexadecimal bitmask that controls which events are logged
for the corresponding provider. Default is 0xFFFFFFFF.
-l, --level <n>
Logging level for the corresponding provider.
Default is 4 (info level).
Logging Parameters
-f, --file-name <name>
Log file name. Default is PktMon.etl.
-s, --file-size <size>
Maximum log file size in megabytes. Default is 512 MB.
-m, --log-mode { circular | multi-file | memory | real-time }
Logging mode. Default is circular.
circular New events overwrite the oldest ones when the log is full.
multi-file No limit on number of captured events, but a new log file
is created each time the log is full.
memory Like circular, but the entire log is stored in memory.
It is written to a file when pktmon is stopped.
real-time Display events and packets on screen at real time. No log
file is created. Press Ctrl+C to stop monitoring.
Example 1: Packet capture
pktmon start --capture
Example 2: Packet counters only
pktmon start --capture --counters-only
Example 3: Event logging
pktmon start --trace -p Microsoft-Windows-TCPIP -p Microsoft-Windows-NDIS
Example 4: Packet capture with event logging
pktmon start --capture --trace -p Microsoft-Windows-TCPIP -k 0xFF -l 4
G8B4Life:
Yep, your version definitely changed from what all the websites put out when it was released.
So, the command after adding the filter for you should be
--- Code: ---pktmon start --capture --pkt-size 0 --trace --file-name rpa.etl
--- End code ---
You won't get any live logging to the screen but when you put in the stop command after running RPA it should show you a summary on screen of how many transmit and receive packets there were.
- Tim
KB02:
That didn't quite work either. When typing in that new code I get:
--- Code: ---Error: Event trace is enabled, but no providers are specified.
--- End code ---
I fiddled and searched and was finnaly able to get this to run:
--- Code: ---pktmon start --capture --file-name rpa.etl
--- End code ---
Not sure if it will even be helpful or not, but I've attached the .pcapng file that I was able to get.
Moderator edit: pcapng file removed for privacy - Tim
G8B4Life:
That's Microsoft for you, according to their docs the event provider is "optional".
Anyway, the capture had everything I wanted in it. I've downloaded it and removed it from your post as it contains more than just RPA's traffic.
Now I'm assuming that RPA did NOT connect when you did the test? (tell me if it did because that's important).
So firstly the good news, there isn't any corruption of the packets, the data going in and out of the WiFi adapter for RPA is correct and the connection sequence is also correct.
Now to the puzzling part; unless the capture is somehow very wrong I'm seeing very strange behavior in the capture, something to do with the WiFi adapter is sending the data in and out repeatedly (usually 4 times) in very quick succession, and I mean nanoseconds! And not just RPA's data either.
So according to the capture RPA and the server negotiated a successful connection 4 times. Also strange is that even if not connected you clicking the pictures button did not get a response from the server which you should have gotten.
I'm looking into it further but it's a weird one for sure.
- Tim
KB02:
Yeah, it was the standard reaction from RPA. I opened it, it said connected, I clicked on the lights button, it thought for a few seconds, then gave me the "Can't connect" message.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version