Multiple IP settings for a client 2

[mikes999]

Is there a way to give a user chance to select a GW server's IP from the client side - for example, user is connecting to the server from different locations, accessing either private or public addresses of the server.

Or, is there a possibility to set up two desktop icons for GW client, with different server IP's?

Thanks,

 

[FarOut]

If you use the "/@u-?" switch (without quotes) on the target line of the properties for the GW Client. The client will stop and prompt for a usename and password. At this point in time you could change the IP address also. If you are running security as LOW and have Notify running, this switch will not work. You would have to exit notify before the switch will be recognized.

Example of Switch: C:\novell\GroupWise\GrpWise.exe /@u-?



FarOut
V-Peace-V

 

[mikes999]

Thanks,FarOut - I knew about this option. The problem lies with users - they are all executives, and don't want to know any stinkin' IP addresses -)...

I need a point'n'click solution - even a couple of patch scripts with respective icons on desktop will suffice.

Thanks nevertheless.

M.S.

 

[FarOut]

Alright, lets try this again. If I undestand you correctly. Two GW icons on the desktop that point to two different IP addresses would be acceptable. If this is so then you can expand on the the "/@u-?" startup switch by adding two additional startup switches. These switches would point one of the GW client icons to a specific IP address and Port assignment. Then you could have another GW client icon pointing to the other IP address and Port assignment.
An example would be:
C:\novell\GroupWise\GrpWise.exe /ipa-167.217.3.100 /ipp-1677 /@U-?.

This would stop and prompt the user for a name and password but would already have the desired IP address you wanted, along with the port assignment. The only drawback is that when one GW icon is used and a user id is entered, the other GW icon will also reflect that change. I hope I understand your question this time, and this was of some help.

FarOut
V-Peace-V

 

[Ed Andres]

What not just use a DNS name instead of an IP address. If you have a DNS server on your network, you could point that entry at the local IP and the public DNS could point to your public IP.

It works for me.
HTH,
Ed

 

[mikes999]

Guys, thank a lot; even though I like the last (DNS) approach better, the 2 shortcuts approach will work because we have multiple PO's, distinguishable only when logging into NDS, which is obviously impossible from the outside..

Thanks!