Exactly.

I've made some changes and we'll see what happens tomorrow.

Thanks for the advice.

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Paul
Keating
Sent: Tuesday, November 08, 2005 1:35 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Very ODD problem with NB5.1MP3a + 2 Solaris
Clients

Oh, so you can ping, telnet, etc from the server to the client? 
It's only the bpcd port that doesn't respond?
...but then hit the server from the client, then the server CAN connect
to the bpcd port on the client?

That's wierder than I thought.

Paul

-----Original Message-----
From: Piszcz, Justin [mailto:jpiszcz AT servervault DOT com] 
Sent: November 8, 2005 1:31 PM
To: Mark.Donaldson AT cexp DOT com; Paul Keating
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Very ODD problem with NB5.1MP3a + 2 Solaris
Clients


Good suggestion, I tried the REQUIRED_INTERFACE, no luck there as it is
not able to "Reach" the open port where bpcd is listening.
The traceroute works fine however and I can ping the box for hours with
0% packet loss, it seems to only affect that port, HMM, I wonder I I
changed the bpcd port?
 

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu