PATHWORKS 7.3 ADVANDCED SERVER

[robert70]

DYNAMIC

Type Destination Gateway

AH 10.208.193.52 129.94.185.1
AH 124.4.104.54 129.94.185.1
AH 127.0.0.1 127.0.0.1
AH 128.4.104.0 129.94.185.1
AH 128.4.104.58 129.94.185.1
AH 128.4.105.0 129.94.185.1
AH 128.4.105.119 129.94.185.1
AH 128.4.106.155 129.94.185.1
AH 128.4.112.3 129.94.185.1
AH 128.4.112.18 129.94.185.1
AH 128.4.112.22 129.94.185.1
AH 128.4.112.61 129.94.185.1
AH 128.4.112.155 129.94.185.1
AH 128.4.112.180 129.94.185.45
AH 128.4.205.50 129.94.185.1
AH 128.4.221.180 129.94.185.1
AH 128.4.236.4 129.94.185.1
AH 128.4.236.25 129.94.185.1
AH 128.4.236.119 129.94.185.1
AH 128.4.237.207 129.94.185.1
AH 128.8.14.126 129.94.185.1
AH 128.8.117.52 129.94.185.1
AH 128.8.127.47 129.94.185.1
AH 128.8.130.2 129.94.185.1
AH 128.8.130.207 129.94.185.1
AH 128.8.135.13 129.94.185.1
AH 128.8.145.108 129.94.185.1
AH 128.8.145.252 129.94.185.1
AH 128.8.176.111 129.94.185.1
AH 128.8.191.79 129.94.185.1
AH 128.8.204.122 129.94.185.1
AH 128.8.209.26 129.94.185.1
AH 128.8.227.2 129.94.185.1
AH 128.8.227.14 129.94.185.1
AH 128.9.79.118 129.94.185.1
AH 128.9.135.16 129.94.185.1
AH 128.9.147.120 129.94.185.1
AH 128.9.165.75 129.94.185.1
AH 128.9.199.140 129.94.185.1
AH 128.9.206.54 129.94.185.1
AH 128.11.28.21 129.94.185.1
AH 128.11.56.61 129.94.185.1
AH 128.11.180.204 129.94.185.1
AH 128.11.184.174 129.94.185.1
AH 128.20.157.5 129.94.185.1
AH 128.20.157.22 129.94.185.1
AH 128.29.109.37 129.94.185.1
AH 128.29.109.38 129.94.185.1
AH 128.29.124.5 129.94.185.1
AH 128.30.67.1 129.94.185.1
AH 128.30.98.1 129.94.185.1
AH 128.30.99.34 129.94.185.1
AH 128.30.100.35 129.94.185.1
AH 128.31.10.58 129.94.185.1
AH 128.31.18.52 129.94.185.1
AH 128.31.18.61 129.94.185.45
AH 128.31.18.61 129.94.185.1
AH 128.31.20.195 129.94.185.1
AH 128.31.46.37 129.94.185.1
AH 128.31.46.38 129.94.185.1
AH 128.63.139.5 129.94.185.1
AH 128.63.181.12 129.94.185.1
AH 128.71.185.0 129.94.185.1
AH 129.94.185.0 129.94.185.1
AH 129.94.185.0 129.94.185.45
AN 129.94.185.0/25 129.94.185.46
AH 129.94.185.1 129.94.185.45
AH 129.94.185.20 129.94.185.20
AH 129.94.185.45 129.94.185.45
AH 129.94.185.46 129.94.185.46
AH 129.94.186.92 129.94.185.1
AH 136.52.46.31 129.94.185.1
AH 136.52.46.89 129.94.185.1
AH 136.52.52.35 129.94.185.1
AH 136.52.52.79 129.94.185.1
AH 136.52.53.33 129.94.185.1
AH 136.52.53.84 129.94.185.1
AH 136.52.53.108 129.94.185.1
AH 136.52.53.237 129.94.185.1
AH 136.52.53.239 129.94.185.1
AH 136.52.56.44 129.94.185.1
AH 136.52.56.108 129.94.185.1
AH 136.52.56.239 129.94.185.1
AH 136.52.57.213 129.94.185.1
AH 136.52.57.254 129.94.185.1
AH 136.54.65.202 129.94.185.1
AN 136.54.80.0/23 129.94.185.1
AN 136.54.82.0/23 129.94.185.1
AN 136.54.100.0/23 129.94.185.1
AH 136.54.100.42 129.94.185.1
AH 136.54.100.60 129.94.185.1
AH 136.54.100.101 129.94.185.1
AH 136.54.100.111 129.94.185.1
AH 136.54.100.144 129.94.185.1
AH 136.54.100.162 129.94.185.1
AH 136.54.101.31 129.94.185.1
AN 136.54.102.0/23 129.94.185.1
AH 136.54.102.59 129.94.185.1
AH 136.54.102.76 129.94.185.1
AH 136.54.102.123 129.94.185.1
AH 136.54.102.130 129.94.185.1
AH 136.54.102.132 129.94.185.1
AH 150.1.3.10 129.94.185.1
AH 150.1.3.11 129.94.185.1
AH 150.1.3.30 129.94.185.1
AH 161.9.20.114 129.94.185.1
AH 161.9.30.114 129.94.185.1
AH 172.19.71.61 129.94.185.1
AH 172.19.71.68 129.94.185.1
AH 172.20.75.61 129.94.185.1
AH 172.27.22.36 129.94.185.1
AH 172.27.32.5 129.94.185.1
AH 192.71.185.172 129.94.185.1

[Hans Hosang]

Robert,
Your PWRK logical looks good, node 46.
yout routing table should only contain routes that lead through nodes .1 and .46.
And I see several that use interface 45.
Also the route through node 20 is still there.

Please remove all routes that specify OTHER than 129.94.185.1 and 129.94.185.46
In other words, routes should only specify your own interface OR the gateway.

[robert70]

many thanks ill try that now

[robert70]

cleared all gateways apart from .1 and .46
still not connecting a share from my pc tp pathworks on 46 server

[robert70]

as i said i can connect from pc 20 to server 46 when i change the server network mask to 255.255.255.0 rather than 255.255.255.128

[Hans Hosang]

Can you make a network trace of the failing connect attempt?

$ tcpdump -s 1518 -w connect.cap host
Then put it in a saveset and mail that to me.

I'd be happier if you also log a call so I can book time on it.

[robert70]

tcpdump not recognised on my system?

[Hans Hosang]

ever heard of @sys$startup:tcpip$define_commands.com ?

Or you are running an ancient TCPIP version.
In that case, use tcptrace but tcpdump is better.

[robert70]

i have tcpdump after all

connect.cap here

[robert70]

this was i was trying to connect a share..................



12:30:07.881933 IP 129.94.185.20.1140 > dave.445: S 505714333:505714333(0) win 6
4512
12:30:07.881933 IP dave.445 > 129.94.185.20.1140: R 0:0(0) ack 505714334 win 0
12:30:07.881933 IP 129.94.185.20.1141 > dave.139: S 3644705880:3644705880(0) win
64512
12:30:07.881933 IP dave.139 > 129.94.185.20.1141: S 3076079008:3076079008(0) ack
3644705881 win 65535
12:30:07.882910 IP 129.94.185.20.1141 > dave.139: P 1:73(72) ack 1 win 64512 NBT
Packet
12:30:07.882910 IP dave.139 > 129.94.185.20.1141: P 1:6(5) ack 73 win 32814 NBT
Packet
12:30:07.882910 IP dave.139 > 129.94.185.20.1141: F 6:6(0) ack 73 win 32814
12:30:07.883886 IP 129.94.185.20.1141 > dave.139: F 73:73(0) ack 6 win 64507
12:30:07.883886 IP dave.139 > 129.94.185.20.1141: . ack 74 win 32813
12:30:07.883886 IP 129.94.185.20.1141 > dave.139: . ack 7 win 64507
12:30:07.883886 IP 129.94.185.20.1142 > dave.139: S 2074612835:2074612835(0) win
64512
12:30:07.883886 IP dave.139 > 129.94.185.20.1142: S 1644653757:1644653757(0) ack
2074612836 win 65535
12:30:07.883886 IP 129.94.185.20.1142 > dave.139: P 1:73(72) ack 1 win 64512 NBT
Packet
12:30:07.884863 IP dave.139 > 129.94.185.20.1142: P 1:5(4) ack 73 win 32850 NBT
Packet
12:30:07.884863 IP 129.94.185.20.1142 > dave.139: P 73:210(137) ack 5 win 64508
NBT Packet
12:30:07.885839 IP dave.139 > 129.94.185.20.1142: P 5:110(105) ack 210 win 32850
NBT Packet
12:30:07.886816 IP 129.94.185.20.1142 > dave.139: P 210:442(232) ack 110 win 644
03 NBT Packet
12:30:07.891698 IP dave.139 > 129.94.185.20.1142: P 110:307(197) ack 442 win 328
50 NBT Packet
12:30:07.895604 IP 129.94.185.20.1142 > dave.139: P 442:762(320) ack 307 win 642
06 NBT Packet
12:30:07.895604 IP dave.139 > 129.94.185.20.1142: P 307:346(39) ack 762 win 3285
0 NBT Packet
12:30:07.897557 IP dave.23 > 129.94.185.20.4741: . 15392:16852(1460) ack 1 win 4
380
12:30:07.900487 IP 129.94.185.20.4741 > dave.23: . ack 16852 win 64512
12:30:07.900487 IP dave.23 > 129.94.185.20.4741: P 16852:17333(481) ack 1 win 43
80
12:30:07.932711 IP 128.31.112.13.6168 > dave.80: S 1263832220:1263832220(0) win
65535
12:30:08.066492 IP 129.94.185.20.4741 > dave.23: . ack 17333 win 64031
12:30:08.066492 IP dave.23 > 129.94.185.20.4741: P 17333:17957(624) ack 1 win 43
80
12:30:08.066492 IP 129.94.185.20.1142 > dave.139: . ack 346 win 64167
12:30:08.269604 IP 129.94.185.20.4741 > dave.23: . ack 17957 win 63407
12:30:08.269604 IP dave.23 > 129.94.185.20.4741: P 17957:18186(229) ack 1 win 43
80
12:30:08.413149 arp who-has 129.94.185.19 tell 129.94.185.17
12:30:08.472716 IP 129.94.185.20.4741 > dave.23: . ack 18186 win 63178
12:30:08.472716 IP dave.23 > 129.94.185.20.4741: P 18186:18406(220) ack 1 win 43
80
12:30:08.608449 IP 128.31.112.13.6168 > dave.80: S 1263832220:1263832220(0) win
65535
12:30:08.675828 IP 129.94.185.20.4741 > dave.23: . ack 18406 win 64512
12:30:08.675828 IP dave.23 > 129.94.185.20.4741: P 18406:18705(299) ack 1 win 43
80
12:30:08.879916 IP 129.94.185.20.4741 > dave.23: . ack 18705 win 64213
12:30:08.879916 IP dave.23 > 129.94.185.20.4741: P 18705:18863(158) ack 1 win 43
80
12:30:09.082052 IP 129.94.185.20.4741 > dave.23: . ack 18863 win 64055
12:30:09.082052 IP dave.23 > 129.94.185.20.4741: P 18863:19021(158) ack 1 win 43
80
12:30:09.285164 IP 129.94.185.20.4741 > dave.23: . ack 19021 win 63897
12:30:09.285164 IP dave.23 > 129.94.185.20.4741: P 19021:19179(158) ack 1 win 43
80
12:30:09.488276 IP 129.94.185.20.4741 > dave.23: . ack 19179 win 63739
12:30:09.488276 IP dave.23 > 129.94.185.20.4741: P 19179:19337(158) ack 1 win 43
80
12:30:09.608385 IP 128.31.112.13.6168 > dave.80: S 1263832220:1263832220(0) win
65535
12:30:09.691388 IP 129.94.185.20.4741 > dave.23: . ack 19337 win 63581
12:30:09.691388 IP dave.23 > 129.94.185.20.4741: P 19337:19636(299) ack 1 win 43
80
12:30:09.894500 IP 129.94.185.20.4741 > dave.23: . ack 19636 win 63282
12:30:09.894500 IP dave.23 > 129.94.185.20.4741: P 19636:19794(158) ack 1 win 43
80
12:30:10.097612 IP 129.94.185.20.4741 > dave.23: . ack 19794 win 63124
12:30:10.097612 IP dave.23 > 129.94.185.20.4741: P 19794:19952(158) ack 1 win 43
80
12:30:10.300724 IP 129.94.185.20.4741 > dave.23: . ack 19952 win 64512
12:30:10.300724 IP dave.23 > 129.94.185.20.4741: P 19952:20110(158) ack 1 win 43
80
12:30:10.503836 IP 129.94.185.20.4741 > dave.23: . ack 20110 win 64354
12:30:10.503836 IP dave.23 > 129.94.185.20.4741: P 20110:20268(158) ack 1 win 43
80
12:30:10.706948 IP 129.94.185.20.4741 > dave.23: . ack 20268 win 64196
12:30:10.706948 IP dave.23 > 129.94.185.20.4741: P 20268:20426(158) ack 1 win 43
80
12:30:10.910060 IP 129.94.185.20.4741 > dave.23: . ack 20426 win 64038
12:30:10.910060 IP dave.23 > 129.94.185.20.4741: P 20426:20584(158) ack 1 win 43
80
12:30:11.113172 IP 129.94.185.20.4741 > dave.23: . ack 20584 win 63880
12:30:11.113172 IP dave.23 > 129.94.185.20.4741: P 20584:20742(158) ack 1 win 43
80
12:30:11.316284 IP 129.94.185.20.4741 > dave.23: . ack 20742 win 63722
12:30:11.316284 IP dave.23 > 129.94.185.20.4741: P 20742:20900(158) ack 1 win 43
80
12:30:11.519396 IP 129.94.185.20.4741 > dave.23: . ack 20900 win 63564
12:30:11.519396 IP dave.23 > 129.94.185.20.4741: P 20900:21058(158) ack 1 win 43
80
12:30:11.628764 IP 128.31.112.13.6168 > dave.80: S 1263832220:1263832220(0) win
65535
12:30:11.722508 IP 129.94.185.20.4741 > dave.23: . ack 21058 win 63406
12:30:11.722508 IP dave.23 > 129.94.185.20.4741: P 21058:21357(299) ack 1 win 43
80
12:30:11.925620 IP 129.94.185.20.4741 > dave.23: . ack 21357 win 63107
12:30:11.925620 IP dave.23 > 129.94.185.20.4741: P 21357:21515(158) ack 1 win 43
80
12:30:12.128732 IP 129.94.185.20.4741 > dave.23: . ack 21515 win 64512
12:30:12.128732 IP dave.23 > 129.94.185.20.4741: P 21515:21673(158) ack 1 win 43
80
12:30:12.331844 IP 129.94.185.20.4741 > dave.23: . ack 21673 win 64354
12:30:12.331844 IP dave.23 > 129.94.185.20.4741: P 21673:21831(158) ack 1 win 43
80
12:30:12.534956 IP 129.94.185.20.4741 > dave.23: . ack 21831 win 64196
12:30:12.534956 IP dave.23 > 129.94.185.20.4741: P 21831:21989(158) ack 1 win 43
80
12:30:12.738068 IP 129.94.185.20.4741 > dave.23: . ack 21989 win 64038
12:30:12.738068 IP dave.23 > 129.94.185.20.4741: P 21989:22147(158) ack 1 win 43
80
12:30:12.941180 IP 129.94.185.20.4741 > dave.23: . ack 22147 win 63880
12:30:12.941180 IP dave.23 > 129.94.185.20.4741: P 22147:22305(158) ack 1 win 43
80
12:30:13.144292 IP 129.94.185.20.4741 > dave.23: . ack 22305 win 63722
12:30:13.144292 IP dave.23 > 129.94.185.20.4741: P 22305:22463(158) ack 1 win 43
80
12:30:13.347404 IP 129.94.185.20.4741 > dave.23: . ack 22463 win 63564
12:30:13.347404 IP dave.23 > 129.94.185.20.4741: P 22463:22621(158) ack 1 win 43
80
12:30:13.550516 IP 129.94.185.20.4741 > dave.23: . ack 22621 win 63406
12:30:13.551492 IP dave.23 > 129.94.185.20.4741: P 22621:22779(158) ack 1 win 43
80
12:30:13.753628 IP 129.94.185.20.4741 > dave.23: . ack 22779 win 63248
12:30:13.754604 IP dave.23 > 129.94.185.20.4741: P 22779:22937(158) ack 1 win 43
80
12:30:13.821006 IP 129.94.185.37.1230 > 255.255.255.255.123: NTPv3 client, strat
0, poll 0, prec 0
12:30:13.956740 IP 129.94.185.20.4741 > dave.23: . ack 22937 win 63090
12:30:13.957716 IP dave.23 > 129.94.185.20.4741: P 22937:23197(260) ack 1 win 43
80
12:30:14.159852 IP 129.94.185.20.4741 > dave.23: . ack 23197 win 64512
12:30:14.160828 IP dave.23 > 129.94.185.20.4741: P 23197:23355(158) ack 1 win 43
80
Interrupt

$ DAVE:SYSTEM>

[Hans Hosang]

you are trying to connect share facility as a user in the hbeu domain.
The answer to this connect request is:
Netlogon not started.
Later it is trying to send a message to administrator but it can't find administrator.

So I guess there is a conflict in the domain and you have configured alerts wrong.

What is your domain config?
Is it a PDC / BDC / Member?
Is it in the same domain as node 45?
If so, what is the role of node 45?

Do you get errors out of:
$ admin show event /full/since

Set the alerts to a proper username so you will get a popup message:
$ regutl set paream * alertnames

[robert70]

>>So I guess there is a conflict in the domain and you have configured alerts wrong.

>>What is your domain config?
via tcpip$configure
core environment
domain

45 server is "chasdomain"
46 server is "bertdomain"

Is it a PDC / BDC / Member?
Is it in the same domain as node 45?
If so, what is the role of node 45?

>>Do you get errors out of:
$ admin show event /full/since

$ DAVE:SYSTEM> admin show event /full/since

Events in System Event Log on server "DAVE":

T Date Time Source Category Event User Computer
- -------- ----------- --------- --------------- ------ ---------- -------------
E 11/03/10 12:02:08 PM NETLOGON None 3097 N/A DAVE
A primary domain controller is already running in this domain.

I 11/03/10 12:02:00 PM Eventlog None 6005 N/A DAVE
The Event log service was started.

E 11/03/10 11:38:32 AM NETLOGON None 3097 N/A DAVE
A primary domain controller is already running in this domain.

I 11/03/10 11:38:24 AM Eventlog None 6005 N/A DAVE
The Event log service was started.

E 11/03/10 11:13:01 AM NETLOGON None 3097 N/A DAVE
A primary domain controller is already running in this domain.

I 11/03/10 11:12:53 AM Eventlog None 6005 N/A DAVE
The Event log service was started.

Total of 6 events

$ DAVE:SYSTEM>

>>Set the alerts to a proper username so you will get a popup message:
$ regutl set paream * alertnames

will set this

[Hans Hosang]

Robert,

You don't seem to have an idea about what a domain is in lanmanager terms.
That has nothing to do with TCPIP (DNS) domains.

The error out of admin is exactly what I expected.
You probably made a copy of node 45 to node 46 and simply upgraded it.
That is the best way into trouble.

What was your idea in doing so?
retain usernames / passwords?
If so, you should make the new one a BDC in the old domain and, when all is done, switch role.

If I'm right, then
- stop pwrk,
- delete *.* in pwrk$lmdomains,
- delete builtin. and lsa. in pwrk$lmdatafiles
- run $ pwconfig and add the server in the old domain as BDC.

If I'm wrong, please provide domain and role info as I requested earlier.
on V7.3B: $ getrole -pwd
server needs to be down for that command
on V6.0 I wouldn't know anymore maybe same command.

[robert70]

>>You probably made a copy of node 45 to node 46 and simply upgraded it.

Yes that is correct

>>What was your idea in doing so?

we are using this 46 as a sort of test bed until we upgrade the 45 box (hopefully this weekend)

>>If I'm right, then
- stop pwrk,

DONE

- delete *.* in pwrk$lmdomains,

DONE

- delete builtin. and lsa. in
pwrk$lmdatafiles

DONE

- run $ pwconfig and add the server in the old domain as BDC.

I GET THIS
1. Run the License Server: YES
2. Enable Timesource service: NO
3. Enable Alerter service: NO
4. Enable Netlogon service: YES
5. Advanced Server domain: CHASDOMAIN
6. Advanced Server role: PRIMARY
7. Advanced Server computer name: DAVE
8. Server announce comment: Advanced Server V7.3B for OpenVMS
9. Advanced Server language: English (USA)
10. Enable NT style printing: NO

[Hans Hosang]

option 6, backup

[robert70]

OPTION 6 BACKUP
JUST REBOOTING ALPHA NOW
WILL LET YOU KNOW IF THIS WORKS

[robert70]

PWRK$CONFIG not letting me change 6 to backup

trying via ......

$ DAVE:SYSTEM> ADMIN
CHASDOMAIN\\DAVE> SET COMPUTER/ROLE = BACKUP
_computer name: DAVE
%PWRK-E-ERRGETSRV, error getting server information for "DAVE"
-LM-E-ERROR_BAD_NETPA, the network path cannot be located

??

[robert70]

IM GETTING THIS VIA THE PWRK$CONFIG ATTEMPTING TO CHANGE primary TO backup

Your Advanced Server for OpenVMS is presently configured to
run as follows:

1. Run the License Server: YES
2. Enable Timesource service: NO
3. Enable Alerter service: NO
4. Enable Netlogon service: YES
5. Advanced Server domain: CHASDOMAIN
6. Advanced Server role: PRIMARY
7. Advanced Server computer name: DAVE
8. Server announce comment: Advanced Server V7.3B for OpenVMS
9. Advanced Server language: English (USA)
10. Enable NT style printing: NO
Enter item number, or RETURN to use these values [DONE]: 6

The Advanced Server role is the part the server will play in its
domain.

A primary domain controller maintains the domain's master user
accounts database and validates logins.

A backup domain controller receives copies of the master database,
validates logins, and can be promoted to primary.

A member server does not receive copies of the master database
or validate logins. It relies on domain controllers to validate
user credentials.

Enter the role of this server (P)rimary/(B)ackup/(M)ember [P]: B

You are attempting to change the role of your server from
primary domain controller to backup domain controller without also
specifying a new domain name.

If your intent is to also change your domain name, please do so
now. You will then be allowed to change your role.

If your intent is to change this server's role in its domain,
please use the ADMININISTER Utility. For more information on
changing your role, please see ADMIN HELP SET COMPUTER/ROLE.

Enter RETURN to continue

[robert70]

IGNORE THE LAST TWO - GOT PAST THAT BIT RE CHANGING 6 TO BACKUP

[robert70]

BUT NOW GETTING THIS?


Enter the role of this server (P)rimary/(B)ackup/(M)ember [P]: B

Before joining a domain, the computer must be added to the
domain. This can be done in one of two ways:

- the administrator of the domain uses the administrative
tools to add this computer to the domain, or

- the computer is added automatically by this procedure;
you must supply an administrator account and password

Are you going to supply account/password information [Y]/N

Enter the name of the primary domain controller for domain CHASDOMAIN:

Enter the name of the primary domain controller for domain CHASDOMAIN: CHASDOMAI
N
Enter the name of the administrator account: [Administrator]
Enter the account password in the required case:
Re-enter to verify password:

Process PWRK$KNBDAEMON created with identification 00000273
Confirming domain name with CHASDOMAIN ...

PWRK-F-COMERR, error communicating with the primary domain controller
Error getting domain name

Since the role selection process failed, the role of your server
is unchanged. If you wish, you may attempt the operation again.
If you choose to exit the selection menu without successfully
choosing a role, you will exit this procedure and the other changes
you have made will not take effect.

Enter RETURN to continue

[robert70]

>>please provide domain and role info as I requested earlier.
on V7.3B: $ getrole -pwd

$ DAVE:SYSTEM> GETROLE -prd
->CHASDOMAIN
->primary
->DAVE

[Hans Hosang]

you need to know your PDC name in order to join a domain.

you can find out by:
$ pwstart tcpip
$ nbshow knbstatus 1B

[Hans Hosang]

that getrole output is logical since DAVE was the second PDC in the domain.
I expect node 45 to be the first one.

see previous reply

[robert70]

>>you can find out by:
$ pwstart tcpip
$ nbshow knbstatus 1B


I presume you mean the 45 box for this command? those commands dont work on that

on the faulty 46 box we get

$ DAVE:SYSTEM> pwstart tcpip
Process PWRK$KNBDAEMON created with identification 000002A5

$ DAVE:SYSTEM> nbshow knbstatus chasdomain 1B
: No response for chasdomain

[Hans Hosang]

what if you do, on the 45, $ nbshow knbstatus

I expect to see a line with <1b> in the soc column.