A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » General XP issues or comments
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Xnews failure update in XP Home



 
 
Thread Tools Display Modes
  #31  
Old November 1st 14, 07:46 PM posted to microsoft.public.windowsxp.general
Paul
external usenet poster
 
Posts: 18,275
Default Xnews failure update in XP Home

KenK wrote:
Paul wrote in :

Your trace above doesn't have enough "NNTP" entries to constitute
a trace of an NNTP session. You should at least be seeing a line
with "nntp", a reference to the outgoing port you've selected
for the session (119). And if we're lucky, a "200" welcome response
from each news server contacted.

You need to turn on more details. IP addresses and so on. Even your
first trace was doing a better job.

If you have a long trace, with full details, copy and paste it into
a pastebin.com window. The pastebin.com window should return a URL,
which you can post here. Just post the URL, and any comments you
might have.

Paul


OK. Made another trace printing with

Packet Summary line
Packet details
All expanded

It's ~650K Too long to post here. Undecipherable to my feeble mind.

First of all, is this what you wanted or so I have to set something else
somewhere in Wireshark?

This Pastebin.com looks VERY complicated. Can you think of another
alternative?

Lastest: Xnews seems to be working with Individual news pretty regularly
using port 8119. Optimax news with port 119 keeps timing out. I tried
using emachine, usually CenturyLink ISP and DSL, with Sitestar dial up
ISP. Still doesn't work with Optimax, though Individual is OK, which I
guess points to emachine problem. Must be a VERY strange problem. I
really don't want to buy a new computer to just read this one news
server.

Now what?

TIA

Ken


Yes, pastebin is very complicated.

1) Go to the source window. In this case, it will be Notepad opening
the Wireshark file you saved.
2) Select all the text. Control-a does select all, or just select all
of it manually.
3) Press control-c to copy (or use "copy" from the edit menu).
4) Go to browser and pastebin.com window. Find the rectangular
area where the paste is to go. Click with the left mouse, to
select that rectangular area. Select "Paste" in your browser
menu or do control-v.
5) You need do to something so pastebin.com will recognize the
rectangle is as full as it is going to get. Scroll down a bit
and click the "Submit" button. Somewhere there, you're going
to get a URL specific to that page of pasted text. That URL
is what you want to copy into a new posting here.

HTH,
Paul

Ads
  #32  
Old November 4th 14, 03:46 PM posted to microsoft.public.windowsxp.general
KenK
external usenet poster
 
Posts: 444
Default Xnews failure update in XP Home

Paul wrote in :

5) You need do to something so pastebin.com will recognize the
rectangle is as full as it is going to get. Scroll down a bit
and click the "Submit" button. Somewhere there, you're going
to get a URL specific to that page of pasted text. That URL
is what you want to copy into a new posting here.



Tried Pastebin again. Submitter this data twice but couldn't find a URL.
Therefore posting here. Hope this is better than last try. BTW, tried a
new version of Xnews - still didn't work. This Wireshark scan is
Thunderbird trying to get Optimax headers.

No.
1 Membership Query, general

Frame 1: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: IPv4mcast_
00:00:01 (01:00:5e:00:00:01)
Internet Protocol Version 4, Src: 192.168.0.1 (192.168.0.1), Dst:
224.0.0.1 (224.0.0.1)
Internet Group Management Protocol

No.
2 Who has 192.168.0.1? Tell 192.168.0.2

Frame 2: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Broadcast
(ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)

No.
3 192.168.0.1 is at 10:5f:06:8f:86:00

Frame 3: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Address Resolution Protocol (reply)

No.
4 Standard query 0xd09d A news.optimax.com

Frame 4: 76 bytes on wire (608 bits), 76 bytes captured (608 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
192.168.0.1 (192.168.0.1)
User Datagram Protocol, Src Port: itm-mccs (3084), Dst Port: domain (53)
Domain Name System (query)

No.
5 Standard query response 0xd09d A 98.100.194.170

Frame 5: 92 bytes on wire (736 bits), 92 bytes captured (736 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 192.168.0.1 (192.168.0.1), Dst:
192.168.0.2 (192.168.0.2)
User Datagram Protocol, Src Port: domain (53), Dst Port: itm-mccs (3084)
Domain Name System (response)

No.
6 jdl-dbkitchen nntp [SYN] Seq=0 Win=65535 Len=0 MSS=1460
SACK_PERM=1

Frame 6: 62 bytes on wire (496 bits), 62 bytes captured (496 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: jdl-dbkitchen (3086), Dst Port:
nntp (119), Seq: 0, Len: 0

No.
7 nntp jdl-dbkitchen [SYN, ACK] Seq=0 Ack=1 Win=16384 Len=0 MSS=
1452 SACK_PERM=1

Frame 7: 62 bytes on wire (496 bits), 62 bytes captured (496 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: jdl-
dbkitchen (3086), Seq: 0, Ack: 1, Len: 0

No.
8 jdl-dbkitchen nntp [ACK] Seq=1 Ack=1 Win=65535 Len=0

Frame 8: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: jdl-dbkitchen (3086), Dst Port:
nntp (119), Seq: 1, Ack: 1, Len: 0

No.
9 Response: 200 Optimax-NNTP, Optimax-Hamster V1.24

Frame 9: 95 bytes on wire (760 bits), 95 bytes captured (760 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: jdl-
dbkitchen (3086), Seq: 1, Ack: 1, Len: 41
Network News Transfer Protocol

No.
10 Request: MODE READER

Frame 10: 67 bytes on wire (536 bits), 67 bytes captured (536 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: jdl-dbkitchen (3086), Dst Port:
nntp (119), Seq: 1, Ack: 42, Len: 13
Network News Transfer Protocol

No.
11 Response: 200 ignored

Frame 11: 67 bytes on wire (536 bits), 67 bytes captured (536 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: jdl-
dbkitchen (3086), Seq: 42, Ack: 14, Len: 13
Network News Transfer Protocol

No.
12 Request: GROUP sdforum.general

Frame 12: 77 bytes on wire (616 bits), 77 bytes captured (616 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: jdl-dbkitchen (3086), Dst Port:
nntp (119), Seq: 14, Ack: 55, Len: 23
Network News Transfer Protocol

No.
13 Response: 211 1966 3 1969 sdforum.general

Frame 13: 87 bytes on wire (696 bits), 87 bytes captured (696 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: jdl-
dbkitchen (3086), Seq: 55, Ack: 37, Len: 33
Network News Transfer Protocol

No.
14 jdl-dbkitchen nntp [ACK] Seq=37 Ack=88 Win=65448 Len=0

Frame 14: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: jdl-dbkitchen (3086), Dst Port:
nntp (119), Seq: 37, Ack: 88, Len: 0

No.
15 xdtp nntp [SYN] Seq=0 Win=65535 Len=0 MSS=1460 SACK_PERM=1

Frame 15: 62 bytes on wire (496 bits), 62 bytes captured (496 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: xdtp (3088), Dst Port: nntp
(119), Seq: 0, Len: 0

No.
16 nntp xdtp [SYN, ACK] Seq=0 Ack=1 Win=16384 Len=0 MSS=1452
SACK_PERM=1

Frame 16: 62 bytes on wire (496 bits), 62 bytes captured (496 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: xdtp
(3088), Seq: 0, Ack: 1, Len: 0

No.
17 xdtp nntp [ACK] Seq=1 Ack=1 Win=65535 Len=0

Frame 17: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: xdtp (3088), Dst Port: nntp
(119), Seq: 1, Ack: 1, Len: 0

No.
18 Response: 200 Optimax-NNTP, Optimax-Hamster V1.24

Frame 18: 95 bytes on wire (760 bits), 95 bytes captured (760 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: xdtp
(3088), Seq: 1, Ack: 1, Len: 41
Network News Transfer Protocol

No.
19 Request: MODE READER

Frame 19: 67 bytes on wire (536 bits), 67 bytes captured (536 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: xdtp (3088), Dst Port: nntp
(119), Seq: 1, Ack: 42, Len: 13
Network News Transfer Protocol

No.
20 Response: 200 ignored

Frame 20: 67 bytes on wire (536 bits), 67 bytes captured (536 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: xdtp
(3088), Seq: 42, Ack: 14, Len: 13
Network News Transfer Protocol

No.
21 Request: GROUP sdforum.pub

Frame 21: 73 bytes on wire (584 bits), 73 bytes captured (584 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: xdtp (3088), Dst Port: nntp
(119), Seq: 14, Ack: 55, Len: 19
Network News Transfer Protocol

No.
22 Response: 211 49723 1 49746 sdforum.pub

Frame 22: 85 bytes on wire (680 bits), 85 bytes captured (680 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: xdtp
(3088), Seq: 55, Ack: 33, Len: 31
Network News Transfer Protocol

No.
23 xdtp nntp [ACK] Seq=33 Ack=86 Win=65450 Len=0

Frame 23: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: xdtp (3088), Dst Port: nntp
(119), Seq: 33, Ack: 86, Len: 0

No.
24 Membership Report / Join group 239.255.255.250 for any sources

Frame 24: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: IPv4mcast_
00:00:16 (01:00:5e:00:00:16)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
224.0.0.22 (224.0.0.22)
Internet Group Management Protocol

No.
25 Who has 192.168.0.2? Tell 192.168.0.1

Frame 25: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Address Resolution Protocol (request)

No.
26 192.168.0.2 is at 00:11:11:5a:b1:0c

Frame 26: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Address Resolution Protocol (reply)

No.
27 rdrmshc bnetgame [PSH, ACK] Seq=1 Ack=1 Win=65127 Len=32

Frame 27: 86 bytes on wire (688 bits), 86 bytes captured (688 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
71.252.193.52 (71.252.193.52)
Transmission Control Protocol, Src Port: rdrmshc (1075), Dst Port:
bnetgame (1119), Seq: 1, Ack: 1, Len: 32
Data (32 bytes)

0000 47 52 4f 55 50 20 73 66 66 2e 70 65 6f 70 6c 65 GROUP sff.people
0010 2e 74 65 72 72 79 2d 6d 63 67 61 72 72 79 0d 0a .terry-mcgarry..

No.
28 bnetgame rdrmshc [PSH, ACK] Seq=1 Ack=33 Win=64465 Len=52

Frame 28: 106 bytes on wire (848 bits), 106 bytes captured (848 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 71.252.193.52 (71.252.193.52), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: bnetgame (1119), Dst Port:
rdrmshc (1075), Seq: 1, Ack: 33, Len: 52
Data (52 bytes)

0000 32 31 31 20 37 31 20 35 32 36 38 20 35 33 34 30 211 71 5268 5340
0010 20 73 66 66 2e 70 65 6f 70 6c 65 2e 74 65 72 72 sff.people.terr
0020 79 2d 6d 63 67 61 72 72 79 20 73 65 6c 65 63 74 y-mcgarry select
0030 65 64 0d 0a ed..

No.
29 rdrmshc bnetgame [PSH, ACK] Seq=33 Ack=53 Win=65075 Len=26

Frame 29: 80 bytes on wire (640 bits), 80 bytes captured (640 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
71.252.193.52 (71.252.193.52)
Transmission Control Protocol, Src Port: rdrmshc (1075), Dst Port:
bnetgame (1119), Seq: 33, Ack: 53, Len: 26
Data (26 bytes)

0000 47 52 4f 55 50 20 73 66 66 2e 61 64 6d 69 6e 2e GROUP sff.admin.
0010 61 6e 6e 6f 75 6e 63 65 0d 0a announce..

No.
30 bnetgame rdrmshc [PSH, ACK] Seq=53 Ack=59 Win=64439 Len=44

Frame 30: 98 bytes on wire (784 bits), 98 bytes captured (784 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 71.252.193.52 (71.252.193.52), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: bnetgame (1119), Dst Port:
rdrmshc (1075), Seq: 53, Ack: 59, Len: 44
Data (44 bytes)

0000 32 31 31 20 35 33 34 20 35 33 20 38 38 33 20 73 211 534 53 883 s
0010 66 66 2e 61 64 6d 69 6e 2e 61 6e 6e 6f 75 6e 63 ff.admin.announc
0020 65 20 73 65 6c 65 63 74 65 64 0d 0a e selected..

No.
31 rdrmshc bnetgame [PSH, ACK] Seq=59 Ack=97 Win=65031 Len=31

Frame 31: 85 bytes on wire (680 bits), 85 bytes captured (680 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
71.252.193.52 (71.252.193.52)
Transmission Control Protocol, Src Port: rdrmshc (1075), Dst Port:
bnetgame (1119), Seq: 59, Ack: 97, Len: 31
Data (31 bytes)

0000 47 52 4f 55 50 20 73 66 66 2e 70 65 6f 70 6c 65 GROUP sff.people
0010 2e 61 6c 61 6e 2d 72 6f 64 67 65 72 73 0d 0a .alan-rodgers..

No.
32 bnetgame rdrmshc [PSH, ACK] Seq=97 Ack=90 Win=64408 Len=53

Frame 32: 107 bytes on wire (856 bits), 107 bytes captured (856 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 71.252.193.52 (71.252.193.52), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: bnetgame (1119), Dst Port:
rdrmshc (1075), Seq: 97, Ack: 90, Len: 53
Data (53 bytes)

0000 32 31 31 20 31 30 32 35 20 38 30 31 35 20 39 31 211 1025 8015 91
0010 31 37 20 73 66 66 2e 70 65 6f 70 6c 65 2e 61 6c 17 sff.people.al
0020 61 6e 2d 72 6f 64 67 65 72 73 20 73 65 6c 65 63 an-rodgers selec
0030 74 65 64 0d 0a ted..

No.
33 rdrmshc bnetgame [PSH, ACK] Seq=90 Ack=150 Win=64978 Len=29

Frame 33: 83 bytes on wire (664 bits), 83 bytes captured (664 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
71.252.193.52 (71.252.193.52)
Transmission Control Protocol, Src Port: rdrmshc (1075), Dst Port:
bnetgame (1119), Seq: 90, Ack: 150, Len: 29
Data (29 bytes)

0000 47 52 4f 55 50 20 73 66 66 2e 70 65 6f 70 6c 65 GROUP sff.people
0010 2e 62 72 6f 6f 6b 2d 77 65 73 74 0d 0a .brook-west..

No.
34 bnetgame rdrmshc [PSH, ACK] Seq=150 Ack=119 Win=64379 Len=47

Frame 34: 101 bytes on wire (808 bits), 101 bytes captured (808 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 71.252.193.52 (71.252.193.52), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: bnetgame (1119), Dst Port:
rdrmshc (1075), Seq: 150, Ack: 119, Len: 47
Data (47 bytes)

0000 32 31 31 20 37 33 20 34 30 31 20 34 37 35 20 73 211 73 401 475 s
0010 66 66 2e 70 65 6f 70 6c 65 2e 62 72 6f 6f 6b 2d ff.people.brook-
0020 77 65 73 74 20 73 65 6c 65 63 74 65 64 0d 0a west selected..

No.
35 rdrmshc bnetgame [PSH, ACK] Seq=119 Ack=197 Win=64931 Len=34

Frame 35: 88 bytes on wire (704 bits), 88 bytes captured (704 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
71.252.193.52 (71.252.193.52)
Transmission Control Protocol, Src Port: rdrmshc (1075), Dst Port:
bnetgame (1119), Seq: 119, Ack: 197, Len: 34
Data (34 bytes)

0000 47 52 4f 55 50 20 73 66 66 2e 70 65 6f 70 6c 65 GROUP sff.people
0010 2e 64 6f 79 6c 65 2d 6d 61 63 64 6f 6e 61 6c 64 .doyle-macdonald
0020 0d 0a ..

No.
36 bnetgame rdrmshc [PSH, ACK] Seq=197 Ack=153 Win=64345 Len=58

Frame 36: 112 bytes on wire (896 bits), 112 bytes captured (896 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 71.252.193.52 (71.252.193.52), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: bnetgame (1119), Dst Port:
rdrmshc (1075), Seq: 197, Ack: 153, Len: 58
Data (58 bytes)

0000 32 31 31 20 31 30 36 34 20 32 31 35 39 35 20 32 211 1064 21595 2
0010 32 36 37 32 20 73 66 66 2e 70 65 6f 70 6c 65 2e 2672 sff.people.
0020 64 6f 79 6c 65 2d 6d 61 63 64 6f 6e 61 6c 64 20 doyle-macdonald
0030 73 65 6c 65 63 74 65 64 0d 0a selected..

No.
37 rdrmshc bnetgame [PSH, ACK] Seq=153 Ack=255 Win=64873 Len=22

Frame 37: 76 bytes on wire (608 bits), 76 bytes captured (608 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
71.252.193.52 (71.252.193.52)
Transmission Control Protocol, Src Port: rdrmshc (1075), Dst Port:
bnetgame (1119), Seq: 153, Ack: 255, Len: 22
Data (22 bytes)

0000 47 52 4f 55 50 20 73 66 66 2e 70 65 6f 70 6c 65 GROUP sff.people
0010 2e 6c 77 65 0d 0a .lwe..

No.
38 bnetgame rdrmshc [PSH, ACK] Seq=255 Ack=175 Win=64323 Len=46

Frame 38: 100 bytes on wire (800 bits), 100 bytes captured (800 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 71.252.193.52 (71.252.193.52), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: bnetgame (1119), Dst Port:
rdrmshc (1075), Seq: 255, Ack: 175, Len: 46
Data (46 bytes)

0000 32 31 31 20 31 31 36 33 20 39 38 33 35 37 20 39 211 1163 98357 9
0010 39 35 32 33 20 73 66 66 2e 70 65 6f 70 6c 65 2e 9523 sff.people.
0020 6c 77 65 20 73 65 6c 65 63 74 65 64 0d 0a lwe selected..

No.
39 rdrmshc bnetgame [PSH, ACK] Seq=175 Ack=301 Win=64827 Len=31

Frame 39: 85 bytes on wire (680 bits), 85 bytes captured (680 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
71.252.193.52 (71.252.193.52)
Transmission Control Protocol, Src Port: rdrmshc (1075), Dst Port:
bnetgame (1119), Seq: 175, Ack: 301, Len: 31
Data (31 bytes)

0000 47 52 4f 55 50 20 73 66 66 2e 70 65 6f 70 6c 65 GROUP sff.people
0010 2e 6d 69 74 63 68 2d 77 61 67 6e 65 72 0d 0a .mitch-wagner..

No.
40 bnetgame rdrmshc [PSH, ACK] Seq=301 Ack=206 Win=64292 Len=54

Frame 40: 108 bytes on wire (864 bits), 108 bytes captured (864 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 71.252.193.52 (71.252.193.52), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: bnetgame (1119), Dst Port:
rdrmshc (1075), Seq: 301, Ack: 206, Len: 54
Data (54 bytes)

0000 32 31 31 20 31 31 32 30 20 38 39 37 33 20 31 30 211 1120 8973 10
0010 31 30 39 20 73 66 66 2e 70 65 6f 70 6c 65 2e 6d 109 sff.people.m
0020 69 74 63 68 2d 77 61 67 6e 65 72 20 73 65 6c 65 itch-wagner sele
0030 63 74 65 64 0d 0a cted..

No.
41 rdrmshc bnetgame [ACK] Seq=206 Ack=355 Win=64773 Len=0

Frame 41: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
71.252.193.52 (71.252.193.52)
Transmission Control Protocol, Src Port: rdrmshc (1075), Dst Port:
bnetgame (1119), Seq: 206, Ack: 355, Len: 0

No.
42 1ci-smcs park-agent [SYN] Seq=0 Win=65535 Len=0 MSS=1460
SACK_PERM=1

Frame 42: 62 bytes on wire (496 bits), 62 bytes captured (496 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
192.168.0.1 (192.168.0.1)
Transmission Control Protocol, Src Port: 1ci-smcs (3091), Dst Port: park-
agent (5431), Seq: 0, Len: 0

No.
43 park-agent 1ci-smcs [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=
1460 SACK_PERM=1

Frame 43: 62 bytes on wire (496 bits), 62 bytes captured (496 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 192.168.0.1 (192.168.0.1), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: park-agent (5431), Dst Port:
1ci-smcs (3091), Seq: 0, Ack: 1, Len: 0

No.
44 1ci-smcs park-agent [ACK] Seq=1 Ack=1 Win=65535 Len=0

Frame 44: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
192.168.0.1 (192.168.0.1)
Transmission Control Protocol, Src Port: 1ci-smcs (3091), Dst Port: park-
agent (5431), Seq: 1, Ack: 1, Len: 0

No.
45 SUBSCRIBE /uuid:105f068f-8600-0086-8f06-
5f105f8f000002/WANPPPConnection:1 HTTP/1.1

Frame 45: 382 bytes on wire (3056 bits), 382 bytes captured (3056 bits)
on interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
192.168.0.1 (192.168.0.1)
Transmission Control Protocol, Src Port: 1ci-smcs (3091), Dst Port: park-
agent (5431), Seq: 1, Ack: 1, Len: 328
Hypertext Transfer Protocol

No.
46 park-agent 1ci-smcs [ACK] Seq=1 Ack=329 Win=6432 Len=0

Frame 46: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 192.168.0.1 (192.168.0.1), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: park-agent (5431), Dst Port:
1ci-smcs (3091), Seq: 1, Ack: 329, Len: 0

No.
47 HTTP/1.1 200 OK

Frame 47: 185 bytes on wire (1480 bits), 185 bytes captured (1480 bits)
on interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 192.168.0.1 (192.168.0.1), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: park-agent (5431), Dst Port:
1ci-smcs (3091), Seq: 1, Ack: 329, Len: 131
Hypertext Transfer Protocol

No.
48 SUBSCRIBE /uuid:105f068f-8600-0086-8f06-
5f105f8f000001/WANCommonInterfaceConfig:1 HTTP/1.1

Frame 48: 390 bytes on wire (3120 bits), 390 bytes captured (3120 bits)
on interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
192.168.0.1 (192.168.0.1)
Transmission Control Protocol, Src Port: 1ci-smcs (3091), Dst Port: park-
agent (5431), Seq: 329, Ack: 132, Len: 336
Hypertext Transfer Protocol

No.
49 HTTP/1.1 200 OK

Frame 49: 185 bytes on wire (1480 bits), 185 bytes captured (1480 bits)
on interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 192.168.0.1 (192.168.0.1), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: park-agent (5431), Dst Port:
1ci-smcs (3091), Seq: 132, Ack: 665, Len: 131
Hypertext Transfer Protocol

No.
50 1ci-smcs park-agent [ACK] Seq=665 Ack=263 Win=65273 Len=0

Frame 50: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
192.168.0.1 (192.168.0.1)
Transmission Control Protocol, Src Port: 1ci-smcs (3091), Dst Port: park-
agent (5431), Seq: 665, Ack: 263, Len: 0

No.
51 jdl-dbkitchen nntp [FIN, ACK] Seq=37 Ack=88 Win=65448 Len=0

Frame 51: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: jdl-dbkitchen (3086), Dst Port:
nntp (119), Seq: 37, Ack: 88, Len: 0

No.
52 nntp jdl-dbkitchen [ACK] Seq=88 Ack=38 Win=65499 Len=0

Frame 52: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: jdl-
dbkitchen (3086), Seq: 88, Ack: 38, Len: 0

No.
53 nntp jdl-dbkitchen [FIN, ACK] Seq=88 Ack=38 Win=65499 Len=0

Frame 53: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: jdl-
dbkitchen (3086), Seq: 88, Ack: 38, Len: 0

No.
54 jdl-dbkitchen nntp [ACK] Seq=38 Ack=89 Win=65448 Len=0

Frame 54: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: jdl-dbkitchen (3086), Dst Port:
nntp (119), Seq: 38, Ack: 89, Len: 0

No.
55 xdtp nntp [FIN, ACK] Seq=33 Ack=86 Win=65450 Len=0

Frame 55: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: xdtp (3088), Dst Port: nntp
(119), Seq: 33, Ack: 86, Len: 0

No.
56 nntp xdtp [ACK] Seq=86 Ack=34 Win=65503 Len=0

Frame 56: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: xdtp
(3088), Seq: 86, Ack: 34, Len: 0

No.
57 nntp xdtp [FIN, ACK] Seq=86 Ack=34 Win=65503 Len=0

Frame 57: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 98.100.194.170 (98.100.194.170), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: nntp (119), Dst Port: xdtp
(3088), Seq: 86, Ack: 34, Len: 0

No.
58 xdtp nntp [ACK] Seq=34 Ack=87 Win=65450 Len=0

Frame 58: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
98.100.194.170 (98.100.194.170)
Transmission Control Protocol, Src Port: xdtp (3088), Dst Port: nntp
(119), Seq: 34, Ack: 87, Len: 0

No.
59 park-agent 1ci-smcs [FIN, ACK] Seq=263 Ack=665 Win=7504 Len=0

Frame 59: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on
interface 0
Ethernet II, Src: Actionte_8f:86:00 (10:5f:06:8f:86:00), Dst: Intel_
5a:b1:0c (00:11:11:5a:b1:0c)
Internet Protocol Version 4, Src: 192.168.0.1 (192.168.0.1), Dst:
192.168.0.2 (192.168.0.2)
Transmission Control Protocol, Src Port: park-agent (5431), Dst Port:
1ci-smcs (3091), Seq: 263, Ack: 665, Len: 0

No.
60 1ci-smcs park-agent [ACK] Seq=665 Ack=264 Win=65273 Len=0

Frame 60: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on
interface 0
Ethernet II, Src: Intel_5a:b1:0c (00:11:11:5a:b1:0c), Dst: Actionte_
8f:86:00 (10:5f:06:8f:86:00)
Internet Protocol Version 4, Src: 192.168.0.2 (192.168.0.2), Dst:
192.168.0.1 (192.168.0.1)
Transmission Control Protocol, Src Port: 1ci-smcs (3091), Dst Port: park-
agent (5431), Seq: 665, Ack: 264, Len: 0

Ken

--
You know it's time to clean the refrigerator
when something closes the door from the inside.






  #33  
Old November 5th 14, 04:04 PM posted to microsoft.public.windowsxp.general
KenK
external usenet poster
 
Posts: 444
Default Xnews failure update in XP Home

KenK wrote in news:XnsA3DB4F0F7C239invalidcom@
130.133.4.11:

This Wireshark scan is
Thunderbird trying to get Optimax headers.


I just looked at the trace I posted. It seems to be for the Sff news
server, not Optimax. I just checked T-bird settings and it is set only
for Optimax news server and during the scan I was trying to get message
headers for Pub group only. I do not know what is going on. T-bird
unsuccessfully trying to get headers for Sff groups. Even if wrong news
server, Xnews gets its (Sff's) groups with no problem.

I'm sorry. I don't know what's going on. sigh I just made another
Wireshark trace and see absolutely nothing I recognize. Came out over
twice as large as last trace. I'm afraid this whole thing is getting
hopeless. Guess I'll have to write off the possibility of reading the
Optimax news sever on my emachine.

Ken


--
You know it's time to clean the refrigerator
when something closes the door from the inside.






  #34  
Old November 5th 14, 08:07 PM posted to microsoft.public.windowsxp.general
Paul
external usenet poster
 
Posts: 18,275
Default Xnews failure update in XP Home

KenK wrote:
Paul wrote in :

5) You need do to something so pastebin.com will recognize the
rectangle is as full as it is going to get. Scroll down a bit
and click the "Submit" button. Somewhere there, you're going
to get a URL specific to that page of pasted text. That URL
is what you want to copy into a new posting here.



Tried Pastebin again. Submitter this data twice but couldn't find a URL.
Therefore posting here. Hope this is better than last try. BTW, tried a
new version of Xnews - still didn't work. This Wireshark scan is
Thunderbird trying to get Optimax headers.


When you click "Submit" on Pastebin, the page will re-display after
a moment. It will look like nothing has changed, but look at the
URL bar in your browser. It will have an additional chunk of characters
on the end of the URL.

Copy the entire (new) URL showing in the URL bar. That is how you
navigate back to the page with the pasted text in it. If you want
to give the text to someone, you give them the URL from the URL
bar, after the Submit button was clicked.

*******

Any time I make dynamic content on the Internet, I "test" the URL
before posting it. For example, with tinypic.com URLs, I open a
separate browser window, paste in the URL, and have a look to see
if what I put up, is still there. You can do the same thing with the
Pastebin one, verify in a new window that your data is there.

Paul
  #35  
Old November 5th 14, 08:23 PM posted to microsoft.public.windowsxp.general
Paul
external usenet poster
 
Posts: 18,275
Default Xnews failure update in XP Home

KenK wrote:
KenK wrote in news:XnsA3DB4F0F7C239invalidcom@
130.133.4.11:

This Wireshark scan is
Thunderbird trying to get Optimax headers.


I just looked at the trace I posted. It seems to be for the Sff news
server, not Optimax. I just checked T-bird settings and it is set only
for Optimax news server and during the scan I was trying to get message
headers for Pub group only. I do not know what is going on. T-bird
unsuccessfully trying to get headers for Sff groups. Even if wrong news
server, Xnews gets its (Sff's) groups with no problem.

I'm sorry. I don't know what's going on. sigh I just made another
Wireshark trace and see absolutely nothing I recognize. Came out over
twice as large as last trace. I'm afraid this whole thing is getting
hopeless. Guess I'll have to write off the possibility of reading the
Optimax news sever on my emachine.

Ken



A question for you. How many LAN connections do you have ?

I have a theory that maybe that trace isn't complete. Wireshark,
you tell it to look at a specific interface. What if you had
a second interface, and some of the packets were on there
instead ?

I would review your network setup, like if you have both Wifi and
Ethernet cable, make sure that things are put together in a
simple-to-understand way.

The reason I say that, is I see

Response: 200 Optimax-NNTP, Optimax-Hamster V1.24 Src: 98.100.194.170 Src Port: nntp (119)
Response: 200 ignored Src: 98.100.194.170 Src Port: nntp (119)

It's almost like another path from your machine is sending
a request as well or something.

If I go to Command Prompt and enter

ipconfig /all

currently I get

Windows IP Configuration

five lines of generic stuff...

Ethernet adapter Local Area Connection 3

...
IP Address 192.168.20.34
...
Lease Obtained
Lease Espires

and there is just the one interface evident there.
I don't have any IPV6 or anything, showing.

Maybe both your wired and wireless are running at the
same time. The OS is supposed to have a solution for that
(metrics), to figure out which path to use, so it's not
supposed to be a problem. Maybe you need Wireshark to collect
info from both. Or alternately, simplify the setup so it's
a bit easier to analyze.

Paul
  #36  
Old November 6th 14, 03:55 PM posted to microsoft.public.windowsxp.general
KenK
external usenet poster
 
Posts: 444
Default Xnews failure update in XP Home

Paul wrote in :

A question for you. How many LAN connections do you have ?

Disconnected them when I hooked up DSL modem to the Ethernet socket on my
emachine. So none. After I get the newsreader working - if I do - I'll work
on LAN. I think I just need to plug Ethernet line from backup system
(Compaq) into CenturyLink DSL modem next to the one from emachine and I'll
get DSL to Compaq and restore LAN.

I have a theory that maybe that trace isn't complete. Wireshark,
you tell it to look at a specific interface. What if you had
a second interface, and some of the packets were on there
instead ?

I would review your network setup, like if you have both Wifi and
Ethernet cable, make sure that things are put together in a
simple-to-understand way.


No Wi-fi. All I have is DSL modem hooked to emachine Ethernet port. Nothing
but CenturyLink ISP connected to DSL modem.

The reason I say that, is I see

Response: 200 Optimax-NNTP, Optimax-Hamster V1.24 Src:
98.100.194.170 Src Port: nntp (119) Response: 200 ignored
Src: 98.100.194.170 Src Port: nntp (119)

The Optimax - Hamster is the news server I'm trying to get headers from
that is not working. Or are you referring to something else I'm missing?
I'm pretty dense. Sorry.

That 119?


It's almost like another path from your machine is sending
a request as well or something.

If I go to Command Prompt and enter

ipconfig /all

currently I get

Windows IP Configuration

five lines of generic stuff...

Ethernet adapter Local Area Connection 3

...
IP Address 192.168.20.34
...
Lease Obtained
Lease Espires

and there is just the one interface evident there.
I don't have any IPV6 or anything, showing.

Maybe both your wired and wireless are running at the
same time. The OS is supposed to have a solution for that
(metrics), to figure out which path to use, so it's not
supposed to be a problem. Maybe you need Wireshark to collect
info from both. Or alternately, simplify the setup so it's
a bit easier to analyze.


Another thing. When I use Xnews on the emachine it connects to Individual
net (Usenet) and Sci-fi (SFF) news servers with no problem. When it tries
to get headers and counts from Optimax it only gets the number of messages
(but not the headers themselves) for the first group, then times out.
Optimax works fine with Xnews on Compaq.

I'll read your message again later when I have more time.


Paul



Ken


--
You know it's time to clean the refrigerator
when something closes the door from the inside.






  #37  
Old November 8th 14, 06:12 PM posted to microsoft.public.windowsxp.general
KenK
external usenet poster
 
Posts: 444
Default Xnews failure update in XP Home

Paul wrote in :

If I go to Command Prompt and enter

ipconfig /all

currently I get

Windows IP Configuration

five lines of generic stuff...

Ethernet adapter Local Area Connection 3

...
IP Address 192.168.20.34
...
Lease Obtained
Lease Espires

and there is just the one interface evident there.
I don't have any IPV6 or anything, showing.



I see the same thing. Nothing about wi-fi, LAN or anything alse I don't
expect.

Ken


--
You know it's time to clean the refrigerator
when something closes the door from the inside.






  #38  
Old November 13th 14, 03:36 PM posted to microsoft.public.windowsxp.general
KenK
external usenet poster
 
Posts: 444
Default Xnews failure update in XP Home

KenK wrote in
:

When I use Xnews on the emachine it connects to Individual
net (Usenet) and Sci-fi (SFF) news servers with no problem. When it
tries to get headers and counts from Optimax it only gets the number
of messages (but not the headers themselves) for the first group, then
times out. Optimax works fine with Xnews on Compaq.


New news. The past two mornings Xnews pulled up the Optimax headers and
messages normally. Unfortunately, back to the usual not working today.

However, though Xnews read and posted ok after I started it, a few hours
later it failed to read or post - while Xnews Usenet connection through
Individual news server continued to work fine. I wonder why it worked
partially. Evidently there's no port number (119) problem? No DSL or DSL
modem problem? No Xnews problem? I don't know. Any new guesses?

Stupidly, I didn't check Thunderbird the days Xnews worked with Optimax.
Might have been interesting.

Ken


--
You know it's time to clean the refrigerator
when something closes the door from the inside.






  #39  
Old November 13th 14, 05:20 PM posted to microsoft.public.windowsxp.general
Paul
external usenet poster
 
Posts: 18,275
Default Xnews failure update in XP Home

KenK wrote:
KenK wrote in
:

When I use Xnews on the emachine it connects to Individual
net (Usenet) and Sci-fi (SFF) news servers with no problem. When it
tries to get headers and counts from Optimax it only gets the number
of messages (but not the headers themselves) for the first group, then
times out. Optimax works fine with Xnews on Compaq.


New news. The past two mornings Xnews pulled up the Optimax headers and
messages normally. Unfortunately, back to the usual not working today.

However, though Xnews read and posted ok after I started it, a few hours
later it failed to read or post - while Xnews Usenet connection through
Individual news server continued to work fine. I wonder why it worked
partially. Evidently there's no port number (119) problem? No DSL or DSL
modem problem? No Xnews problem? I don't know. Any new guesses?

Stupidly, I didn't check Thunderbird the days Xnews worked with Optimax.
Might have been interesting.

Ken


Well, we always like "cheerily non-reproducible" results on a computer :-)
While the problem could be at the ISP end, I don't see a reason for it.
My ISP here doesn't screw around too much. The previous ISP did a few
things, but there was usually an email stream with some advanced notice.

On your end of things, were there any network configuration differences ?
Another device connected to the router ? Different software running
on the machine itself ?

There was a case a couple weeks ago, of a strange network outage,
and it was a dirty NIC connector. Unplugging and replugging fixed it.
The symptoms there, were lots of things worked, and one specific
thing did not. Exactly how you could get a dirty connector
to do that just doesn't make sense. But that's the world
we live in.

Paul
  #40  
Old November 13th 14, 06:50 PM posted to microsoft.public.windowsxp.general
KenK
external usenet poster
 
Posts: 444
Default Xnews failure update in XP Home

Paul wrote in :

On your end of things, were there any network configuration
differences ?


Nope.

Another device connected to the router ? Nope.



Nope.

Different software running
on the machine itself ?


Nope.

Obviously the machine has been hexed by an enemy. Didn't know I had any.
sigh

I'll let you know of any interesting new symptoms.

Ken


--
You know it's time to clean the refrigerator
when something closes the door from the inside.






 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 04:49 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.