Remote users dropping connectivity to the commonspace

[bhawley]

We are running Pro/E WF3 and Ilink 3.4 m040 with 10-30 users at a time.




Our company is in the middle of a carefully staged move of all 600 of us
and all the machines we use to make our stuff. We are moving from
downtown Seattle to a new location 20 miles north. Our IT department has
done a marvelous job with supplying a 100 Mb pipeline one way and 200 Mb
the other. When pinging data server by name from the new location we get
between 3 and 6 ms round-trip times. It is a single network it is all
within the same domain.



We started moving the engineering community with the first two victims
up there already. Thank goodness it's only two design engineers who have
moved so far. Intralink starts up fine, you can check things out,
refresh, sync with the common space, then just wait 10 to 15 minutes and
your connectivity to data server goes away.



Is there a wide area network timing setting parameter or something that
can help me keep these guys connected and the rest of us as we move up
in stages?



Thanks

Brian

[DanielReid]

Hi Brian,

That seems a bit odd. I'm still on Pro/I 3.3 with WF2 but when we
re-located our servers from our local office in Kirkland to the IT
division office in Renton I didn't have to make any system changes at
all. It's a 1Gb fiber link (long fiber) but the latency is still about
3ms so it isn't too different. We don't use anywhere near the 1Gb
potential so I imagine your 100Mb-200Mb pipe should be fine, and 3ms-6ms
should be fine unless 3.4 got worse than 3.3. I have locations running
okay with up to 200ms latency and much lower bandwidth and never heard
of anything to tune or adjust. Would be nice perhaps but just not
there.

Are you sure the network connection is consistently 3ms-6ms and doesn't
have any drops?

Does their connection to the dataserver ever come back without
restarting Pro/I?

[bnemec]

I suffer fromthe same problem. I currentlyuse WF2 and ILINK 3.3 over a 1MB DSL for remote work. After Intralink is open for a period of time it loses connection to database. I can continue using Pro/E and saving work to local workspace. But, any Commonspace actions require restarting Intralink.

Please post summary if you find any resolution to this situation.

Thank you,

Brian Nemec