PATHWORKS 7.3 ADVANDCED SERVER

[Steven Schweda]

It's like pulling teeth with your bare hands.

> 2 alpha ds20e on same network

> alpha

Which "alpha" is this? The one which works?
The one which doesn't?

Which part of "all" is so difficult to
understand?

Do you really expect to get any useful (free)
advice if you refuse to supply any (or
enough) useful information (as repeatedly
requested)?


> [...] Only addresses > .128 will "get
> masked in".

Huh?

[robert70]

yes sorry the alpha DAVE is the one that isnt working

[Sam Samalsson]

Class B net
netmask 255.255.255.128
network 129.94.185.0
broadcast 129.94.185.127
host addresses from 129.94.185.1 to 129.94.185.126

Are you within the limits on all the hosts ?
Do you have address conflicts on your subnet ?

Check the log files and event logs.

Check the TCPIP setup on all your hosts together with a friend.

Good luck !

[robert70]

>Are you within the limits on all the hosts ?

yes - the hosts are 45 and 46

>Do you have address conflicts on your subnet ?

no

[Hans Hosang]

Then, Robert, they "should" be able to speak with eachother.

Next thing I would check is the IP gateway.
Is this gateway within the IP range Sam indicated?
If not, that could be your problem.

PC: ipconfig /all
VMS: tcpip sho route

[Hans Hosang]

Other option;
Is your issue with PWRK ONLY?
Does telnet and other IP communication work well?
Do you have multiple IP interfaces in the box?
If so, do you have defined pwrk$knbdaemon_device logical name to the wrong interface?

[robert70]

Next thing I would check is the IP gateway.
Is this gateway within the IP range Sam indicated?
the gateway is 129.94.185.1

If not, that could be your problem.

PC: ipconfig /all
my pc shows this
Description . . . . . . . . . . . : Broadcom NetXtreme
Physical Address. . . . . . . . . : 00-16-35-61-9A-EF
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 129.94.185.20
Subnet Mask . . . . . . . . . . . : 255.255.255.128
Default Gateway . . . . . . . . . : 129.94.185.1


VMS: tcpip sho route
here is a sample of this showing the 2 servers 45 and 46

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

[robert70]

Other option;

Is your issue with PWRK ONLY?
YES

Does telnet and other IP communication work well?
YES

Do you have multiple IP interfaces in the box? no

TCPIP> show interface
Packets
Interface IP_Addr Network mask Receive Send MTU

IE0 129.94.185.46 255.255.255.128 67388 16520 1500
LO0 127.0.0.1 255.0.0.0 795 795 4096

If so, do you have defined pwrk$knbdaemon_device logical name to the wrong interface?

$ DAVE:SYSTEM> show log pwrk$knbdaemon_device
"PWRK$KNBDAEMON_DEVICE" = "EIA0:" (LNM$SYSTEM_TABLE)

[Hans Hosang]

Robert, it would have been handy if you would have splitup the 2 tables from the 2 alpha's, now its one bunch of spaghetty.
But, what I see sounds very wrong to me.
In the routing table i see:

AH 129.94.185.20 129.94.185.20

So here you are telling VMS that if it needs to send traffic to your PC (129.94.185.20) through interface 129.94.185.20.
It doesn't have an interface 129.94.185.20.
So that will fail.

please remove that route

[robert70]

i see what you mean
i have removed this