Anonymous_User Absent Member.
Absent Member.
1074 views

Re: remote sites

Sorry, The old servers fro Network "A" will be shut down when the
Network "B" is up and running.

Andy Konecny wrote:
> In article <3EB144EC.9070101@bellsouth.net>, Charles Redfearn wrote:


>
>>Network "A" 4 servers; PHN-GPS-01, PHN-GPS-02, PHN-IMAX, & PHN-ENX.


>>Network "B" 3 servers; PHN-GPS-01, PHN-IMAX, & PHN-ENX.
>>

>
> Same names? Hopefully not at the same time, but from your message

sounds
> like you already have the new system built. That's a recipe for

problems
> right there even if they are different versions.
>
> If you need/want to keep the same server names, the preferred method

would
> be to use either the Migration Wizard or the Server Consolidation

Tool.
>
> for the remote offices to connect to the NetWare 4.11 systems, the

routes
> through you ISP must be carrying IPX or someone has had the 'fun' of


> configuring NetWare/IP. Knowing which is in use will help on the

move
> forward.
>
> Are you changing the lines from the remote sites or are they staying

the
> same?
>
>
>
>>So my questions are:
>>How do I get the N6 servers to advertise their existence?

>
> Either via IPX SAPs in which you will have a problem because of

conflicts
> with the old servers, or via SLP which does not automatically flow

over
> routers (either tell the routers the right helper addressing or

configure
> a SLPDA and tell the workstations about it)
>
>
>>Do I have to set up SLP?

>
> Very likely
>
>
>>Do I need to set up VPN’s?

>
> Depends, are those ISP links shared or already private?
> IPX doesn't tend to work via most VPN's. So far I've only seen IPX

work
> over BorderManager's VPNs
>
>
>>Would getting my servers put into the DNS record of my ISP do the

trick?
>
> No, not that there isn't any value, but I wouldn't jump on that

without
> really thinking the security implications of that.
>
>
>>What else am I forgetting?

>
> Probably tonnes but that is hard to catch in this context. You

could
> probably really benefit from at least a day's worth of consulting

time
> with someone such as myself who has done these migrations before to

get
> you on the right track. Check your local Novell office for a good > integrator near you. If you were closer I'd have my hand up, but

your
> border guards just don't like letting us 'foreigners' come work in

your
> country 😉
>
>
> Andy Konecny
> Ainsworth Inc. in Toronto (a few elderly folks get a little flue

and
> everyone panics, where few is less than the # of people killed in

car
> accidents)
> [sometimes being certifiable is more fun than being certified :]
>





Labels (1)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: remote sites

In article <3EB2A7F0.9030100@bellsouth.net>, Charles Redfearn wrote:
> Sorry, The old servers fro Network "A" will be shut down when the
> Network "B" is up and running.
>

So you have Network "B" running in isolation with all the same network

addresses (IPX & IP) and have tried at least one swap that didn't
work?


Andy Konecny
Ainsworth Inc. in Toronto
[sometimes being certifiable is more fun than being certified :]




0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.