| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 24.1 | Overwhelmed | UTRTSC::SWEEP | | Tue Jul 09 1996 12:34 | 19 |
| 24.2 | | TOHOPE::VORE_S | I would like to buy a fish license... | Wed Jul 10 1996 20:45 | 2 |
| 24.3 | | TOHOPE::VORE_S | I would like to buy a fish license... | Wed Jul 10 1996 20:46 | 1 |
| 24.4 | | VMSNET::P_NUNEZ | | Wed Jul 10 1996 23:49 | 14 |
| 24.5 | We have .2 | UTRTSC::SWEEP | | Tue Jul 16 1996 14:14 | 9 |
| 24.6 | | UTRTSC::SWEEP | | Tue Jul 16 1996 14:17 | 10 |
| 24.7 | Workstation Service? | VMSNET::P_NUNEZ | | Tue Jul 16 1996 15:51 | 10 |
| 24.8 | workstation service | TOHOPE::VORE_S | I would like to buy a fish license... | Tue Jul 16 1996 21:39 | 34 |
| 24.9 | Tool or Requirement ??? | UTRTSC::SWEEP | | Thu Jul 18 1996 13:24 | 25 |
| 24.10 | | TOHOPE::VORE_S | I would like to buy a fish license... | Thu Jul 18 1996 15:56 | 15 |
| 24.11 | | UTRTSC::SWEEP | | Fri Jul 19 1996 10:33 | 12 |
| 24.12 | well you did ask.... | KERNEL::IMBIERSKIT | Good frames, Bad frames... | Mon Jul 22 1996 11:07 | 30 |
| 24.13 | | UTRTSC::SWEEP | | Mon Jul 22 1996 11:27 | 13 |
| 24.14 | | KERNEL::IMBIERSKIT | Good frames, Bad frames... | Mon Jul 22 1996 12:18 | 15 |
| 24.15 | | UTRTSC::SWEEP | | Mon Jul 22 1996 15:50 | 18 |
| 24.16 | No Restart Required? | VMSNET::P_NUNEZ | | Mon Jul 22 1996 16:25 | 7 |
| 24.17 | incl debuglmsrc.c | UTRTSC::SWEEP | | Mon Jul 22 1996 17:12 | 18 |
| 24.18 | | UTRTSC::SWEEP | | Mon Jul 22 1996 17:12 | 71 |
| 24.19 | Any news on this? | VMSNET::P_NUNEZ | | Fri Sep 13 1996 16:13 | 21 |
| 24.20 | | UTRTSC::SWEEP | | Fri Sep 13 1996 18:06 | 32 |
| 24.21 | turning on debug trace in an active server | CPEEDY::MOTYL | | Mon Sep 16 1996 16:35 | 116 |
| 24.22 | | UTRTSC::SWEEP | | Tue Sep 17 1996 13:08 | 6 |
| 24.23 | | UTRTSC::SWEEP | | Tue Sep 17 1996 13:14 | 38 |
| 24.24 | The Price of Debug Mode? | VMSNET::P_NUNEZ | | Tue Sep 17 1996 15:50 | 14 |
| 24.25 | | UTRTSC::SWEEP | | Wed Sep 18 1996 10:45 | 11 |
| 24.26 | | UTRTSC::EISINK | Fly by wire | Thu Sep 19 1996 12:45 | 7 |
| 24.27 | System group logicals. | UTRTSC::EISINK | Fly by wire | Thu Sep 19 1996 12:47 | 3 |
| 24.28 | Trouble with DEBUG.COM | VMSNET::P_NUNEZ | | Mon Sep 23 1996 22:55 | 36 |
| 24.29 | missing parameter? | CPEEDY::MOTYL | | Mon Sep 23 1996 23:13 | 14 |
| 24.30 | Pilot Error | VMSNET::P_NUNEZ | | Tue Sep 24 1996 16:14 | 8 |
| 24.31 | | UTRTSC::EISINK | Fly by wire | Wed Sep 25 1996 09:36 | 2 |
| 24.32 | | VMSNET::P_NUNEZ | | Wed Sep 25 1996 20:45 | 7 |
| 24.33 | | UTRTSC::EISINK | Fly by wire | Thu Sep 26 1996 09:02 | 2 |
| 24.34 | | UTRTSC::SWEEP | | Thu Sep 26 1996 09:42 | 11 |
| 24.35 | New tools that were requested by YOU!! | UTRTSC::SWEEP | I want a lolly... | Fri Jan 31 1997 12:26 | 91 |
| In reply to a number of requests.
In V6 we will have a nr of tool extentions.
Yes We have the SMB generator. It is a tool that is
currently used to test the V6 server. We can see if we
can make the tool available to the field.
Yes We have PWRK$SDA extentions so that you can see a
lot about what is going on in the server and they can help
in dump analysis. See a note later in this section about a
description of the tool. (user guide) This tool will be in
the kit.
Yes we have logging that you can enable/disable on the fly.
I have the prototype working. I am planning to logg:
1) SMBs
2) Connections
3) NET LOGONS
4) Replication
You have a control program to enable/disable it and to select
which function you want to trace. You trace into a global sec-
tion, so there will be NO performance overhead.
When your done tracing, you need a viewer to read the data in
the file that was used as a backing store for the global section.
Here is the output of the prototype (there will be a windows
viewer, like the Win NT event viewer and a VAX log file conv).
The output here is from the VAX log file convertor.
Nr of data blocks : 799
Nr of logged messages: 12
Time Type
---- ----
Fri Jan 31 11:29:28 SMBS(C) err:00-0000 com: SMBnegprot
Fri Jan 31 11:29:29 SMBS(C) err:00-0000 com: SMBsesssetup
Fri Jan 31 11:29:29 SMBS(C) err:00-0000 com: SMBtconX
Fri Jan 31 11:29:31 SMBS(C) err:00-0000 com: SMBsearch
Fri Jan 31 11:29:31 SMBS(C) err:00-0000 com: SMBsearch
Fri Jan 31 11:29:32 SMBS(C) err:00-0000 com: SMBsearch
Fri Jan 31 11:29:32 SMBS(C) err:00-0000 com: SMBdskattr
Fri Jan 31 11:29:34 SMBS(C) err:00-0000 com: SMBopen
Fri Jan 31 11:29:34 SMBS(C) err:00-0000 com: SMBreadX
Fri Jan 31 11:29:34 SMBS(C) err:00-0000 com: SMBclose
Fri Jan 31 11:29:36 SMBS(C) err:00-0000 com: SMBtdis
Fri Jan 31 11:29:36 SMBS(C) err:00-0000 com: SMBulogoff
and full data using -f
Time Type
---- ----
Fri Jan 31 11:29:28 SMBS(C) SMBnegprot
com : 72
rcls : 00
err : 0000
flg : 00
tid : 0000
pid : 0000
uid : 0800
mid : 0003
nvwv : 06
vwv[00] : 0000
vwv[01] : 0000
vwv[02] : 0000
vwv[03] : 0000
vwv[04] : 0000
vwv[05] : 0000
ndata : 0000
Fri Jan 31 11:29:29 SMBS(C) SMBsesssetup
com : 73
rcls : 00
err : 0000
flg : 00
tid : 3300
pid : 002A
uid : 1000
mid : 0A03
nvwv : 06
vwv[00] : 0066
vwv[01] : 0864
vwv[02] : 0000
vwv[03] : 0000
vwv[04] : 0000
vwv[05] : 0000
ndata : 0075
etcetera.
You see, we listen...
Adrie
|
| 24.36 | Hallelujah!!!!! | VMSNET::P_NUNEZ | | Fri Jan 31 1997 15:38 | 17 |
|
Adrie,
This stuff is going to be invaluable. Especially the replication
logging as in v5 there's nearly nothing in this area. I see domain
replication being one of the biggest areas the CSC will get calls on.
It's been a real thorn to troubleshoot in v5.
Any chance you guys will produce a training session/tape on pwrk$sda?
Also, is any type of "exerciser" going to be available? I.e.,
something to run from the server to verify setup/connectivity/etc
(like they currently have for the DEC UNIX server)?
Paul
(who can't emphasize enough how wonderful your news is - thank you a
million times!)
|
| 24.37 | Yep | UTRTSC::SWEEP | I want a lolly... | Mon Feb 10 1997 10:46 | 16 |
| Yes there will be a v6 videosession in which we will
demonstrate the tools and explain all nitty gritties.
Yes there is an exerciser but its only used in our labs.
We are trying to get them to the field. Its the same
one (I think) as the one in osf.
Only 30% of our task towards the field has been done.
The agenda is:
1) Implement tracing in V6.
2) Prepare video sessions. A note will be placed in this
notes file soon, requesting inputs on our ideas.
3) Make and present video sessions and additional material
(Find a more suitable distribution mechanism).
Adrie
|
| 24.38 | | VMSNET::P_NUNEZ | | Mon Feb 10 1997 19:22 | 11 |
|
How much work would it be to extend the capabilities of:
$ MC PCSA_CLAIM_NAME /STATUS
$ MC PWRK$NBSHOW <option>
to accept a NETBIOS name (have it do a findname request and report
the results - like SHOW ASTAT <name> /LANA:n or NET DIAG /STATUS or
NBTSTAT -a)?
Paul
|
| 24.39 | None at all | UTRTSC::SWEEP | I want a lolly... | Wed Feb 12 1997 09:11 | 4 |
| We have it.
I will ask rob E. to put it online.
Adrie
|
| 24.40 | | VMSNET::P_NUNEZ | | Thu Feb 13 1997 21:54 | 10 |
|
What about getting pcsa_claim_name to also include the output from
current DECNET/NETBIOS sessions, like $ NBSHOW NBSTATUS | KNBSTATUS do?
I know you can see the links with $ MC NCP SHOW KNOWN LINKS, but one of
the things I see with NBSHOW that I like is whether the user is
connected via the PATHWORKS cluster alias or the specific nodename (in
the session status area).
Paul
|
| 24.41 | | UTRTSC::SWEEP | I want a lolly... | Fri Feb 14 1997 09:45 | 7 |
| Session services doesn't go via the NETBIOS process, but via
the DECnet alternate QIO interface code which is in PCFSDRIVER.
So there is no way we can do this, we simply use DECnet so
NCP sho KNO links is the only way.
Adrie
|
| 24.42 | Decode v5 SMB? | VMSNET::P_NUNEZ | | Fri Feb 28 1997 17:25 | 20 |
| Re .17 & .18
For us uninitiated, would it be possible to map what I see in a v5 SMB
packet to the parsing code in .18? For example, given the SMB of:
10:41:43 006FB230(smbwork) LM$BLD_ROOT:[LM.SERVER.CTRL.SRC]SMBWORK.C;1
716 SMBRCVD 138 bytes:
FF 53 4D 42 73 00 00 00 00 08 00 00 00 00 00 00 .SMBs...........
00 00 00 00 00 00 00 00 00 00 1B 08 00 00 00 00 ................
0A FF 00 00 00 04 11 00 00 00 00 00 00 00 00 18 ................
00 00 00 00 00 53 00 45 DF AE 35 4A AA F1 9D A5 .....S.E�<XAE>5J��.�
9C 00 6C F6 58 8C EA A9 BF 1F 72 89 E4 B4 22 41 ..l�X.ꩿ.r.�<XB4>"A
44 4D 49 4E 00 4E 42 41 00 56 4D 53 20 20 47 37 DMIN.NBA.VMS G7
2E 31 00 50 41 54 48 57 4F 52 4B 53 20 56 35 20 .1.PATHWORKS V5
66 6F 72 20 4F 70 65 6E 56 4D 53 20 28 4C 41 4E for OpenVMS (LAN
20 4D 61 6E 61 67 65 72 29 00 Manager).
how would one determine the value for each of the SMB fields?
Paul
|
| 24.43 | | UTRTSC::SWEEP | I want a lolly... | Mon Mar 03 1997 10:17 | 16 |
| Yep, no problem.
Take the smb specs that are in the PWTOOLS directory. In the beginning
of the specs you find the SMB layout. At the appending you will find
all error codes and command codes.
The only thing to keep in mind is that when you have a WORD that you
need to swap the 2 bytes in a WORD before adding them up. So 00 01
is actually 01 00, and 00 fe = fe 00.
As a lab exer. Make a connection from a pc to a server, make sure you
have smb logging enabled, an iris trace and the spec's printed out.
Now with the spec's attack the smb's in the log file and use iris to
validate your results.
Adrie
|
| 24.44 | | JAMIN::WASSER | John A. Wasser | Mon Mar 03 1997 19:28 | 34 |
| > how would one determine the value for each of the SMB fields?
Offset Size value Meaning
0 4 FF 53 4D 42 (Signature = "\xFFSMB")
4 1 73 (smb_com)
5 1 00 (smb_rcl)
6 1 00 (unused?)
7 2 00 00 (smb_err)
9 15 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (unused?)
24 2 00 00 (smb_tid)
26 2 1B 08 (smb_pid = 0x081B)
28 2 00 00 (smb_uid)
30 2 00 00 (smb_mid)
32 1 0A (Parameter word count = 10)
FF 00 (Parameter word 1 = 0x00FF)
00 00 (Parameter word 2)
04 11 (Parameter word 3 = 0x1104)
00 00 (Parameter word 4)
00 00 (Parameter word 5)
00 00 (Parameter word 6)
00 00 (Parameter word 7)
18 00 (Parameter word 8 = 0x0018)
00 00 (Parameter word 9)
00 00 (Parameter word 10)
53 00 (Parameter Byte Count = 0x0053)
0x53 (Byte Parameters)
45 DF AE 35 4A AA F1 9D A5 E�.5J��.�
9C 00 6C F6 58 8C EA A9 BF 1F 72 89 E4 B4 22 41 ..l�X.ꩿ.r.�."A
44 4D 49 4E 00 4E 42 41 00 56 4D 53 20 20 47 37 DMIN.NBA.VMS G7
2E 31 00 50 41 54 48 57 4F 52 4B 53 20 56 35 20 .1.PATHWORKS V5
66 6F 72 20 4F 70 65 6E 56 4D 53 20 28 4C 41 4E for OpenVMS (LAN
20 4D 61 6E 61 67 65 72 29 00 Manager).
|