DHCP and D4GL WTK Client

We're considering implementing DHCP for all our client PCs. Servers will remain with fixed IP addresses. Are there any concerns that we need to be aware of that would impact on the proper running of our D4GL WTK Client on a DHCP-configured PC? Two things that cause me to ask this question: - When you login for the first time after installation, you get prompted to confirm authorization for <username> on <client IP address>. Does this eman that licensing is handled using IP addresses? If yes, would we expect users to have to answer this prompt everytime they login and receive a different IP address? - We use a script to transfer TEXT blob data to the client and present it in Wordpad for the user to modify or view. It uses the FGLSERVER parameter to get the IP address of the client for proper network file transfer. DHCP won't interfere with this, right (I'm thinking it shouldn't, but confirmation would be nice)? TIA! Best regards, Edmund Nigel Gall Senior Information Systems Specialist Process Plant Services Limited Atlantic Avenue, Point Lisas Industrial Estate Point Lisas, Couva, Trinidad & Tobago, W.I. Tel: (868) 636 2906 x 274 Fax: (868) 679 3770

Nigel Gall wrote: > > We're considering implementing DHCP for all our client PCs. Servers will > remain with fixed IP addresses. Are there any concerns that we need to be > aware of that would impact on the proper running of our D4GL WTK Client on a > DHCP-configured PC? Two things that cause me to ask this question: DHCP clients are not a problem; DHCP servers are. So, thus far, you are fine. > - When you login for the first time after installation, you get prompted to > confirm authorization for <username> on <client IP address>. Does this eman > that licensing is handled using IP addresses? If yes, would we expect users > to have to answer this prompt everytime they login and receive a different > IP address? I know the popup you mean. I've forgotten (assuming I ever knew) why that happens and how you suppress it. I'm sure there is a way to do it, but... Drat, I hate it when I start to answer and can't finish! > - We use a script to transfer TEXT blob data to the client and present it in > Wordpad for the user to modify or view. It uses the FGLSERVER parameter to > get the IP address of the client for proper network file transfer. DHCP > won't interfere with this, right (I'm thinking it shouldn't, but > confirmation would be nice)? Should be fine. > Edmund Nigel Gall > Senior Information Systems Specialist > Process Plant Services Limited > Atlantic Avenue, Point Lisas Industrial Estate > Point Lisas, Couva, Trinidad & Tobago, W.I. > Tel: (868) 636 2906 x 274 Fax: (868) 679 3770 -- Yours, Jonathan Leffler (Jonathan.Leffler@Informix.com) #include <disclaimer.h> Guardian of DBD::Informix v1.00.PC1 -- http://www.perl.com/CPAN "I don't suffer from insanity; I enjoy every minute of it!"

Jonathan Leffler wrote: > Nigel Gall wrote: > > > > We're considering implementing DHCP for all our client PCs. Servers will > > remain with fixed IP addresses. Are there any concerns that we need to be > > aware of that would impact on the proper running of our D4GL WTK Client on a > > DHCP-configured PC? Two things that cause me to ask this question: > > DHCP clients are not a problem; DHCP servers are. So, thus far, you are > fine. > > > - When you login for the first time after installation, you get prompted to > > confirm authorization for <username> on <client IP address>. Does this eman > > that licensing is handled using IP addresses? If yes, would we expect users > > to have to answer this prompt everytime they login and receive a different > > IP address? > > I know the popup you mean. I've forgotten (assuming I ever knew) why > that > happens and how you suppress it. I'm sure there is a way to do it, > but... > Drat, I hate it when I start to answer and can't finish! > This message appears the first time a user starts an 4GL application that connects to the graphical daemon running on the Client computer. This message also appears when you make a 'rcp', 'rcmd' from a server to computer on which the WTK client is installed. If you answer 'Yes' to the messagebox this means that user on the remote computer will have access to the local computer for all future connection. The user name and the computer name are recorded in the <WINDOWS DIRECTORY>\\rhosts file. If you answer 'Only once', that means that user on the remote computer can access to your computer only this time. If you answer 'No' access is denied for user on the remote computer. In the file <WINDOWS DIRECTORY>\\rhosts, you will have the following entries computer.domain.com user 127.0.0.1 user 10.0.0.1 user If you used a DHCP address for the server, you will prompt to autorise user from the remote system each time the ip address change. > > > - We use a script to transfer TEXT blob data to the client and present it in > > Wordpad for the user to modify or view. It uses the FGLSERVER parameter to > > get the IP address of the client for proper network file transfer. DHCP > > won't interfere with this, right (I'm thinking it shouldn't, but > > confirmation would be nice)? > > Should be fine. > With the WTK you can add to connection string the following tag '@FGL' There are several tags like @FGL --> FGLSERVER=<IP>:<PORT>;export FGLSERVER;FGLGUI=1;export FGLGUI @FGLNT --> set FGLSERVER=<IP>:<PORT>;set FGLGUI=1 In this case even you IP address is changed by the DHCP server. You will have always the right value for your FGLSERVER environment variable. > > > Edmund Nigel Gall > > Senior Information Systems Specialist > > Process Plant Services Limited > > Atlantic Avenue, Point Lisas Industrial Estate > > Point Lisas, Couva, Trinidad & Tobago, W.I. > > Tel: (868) 636 2906 x 274 Fax: (868) 679 3770 > > -- > Yours, > Jonathan Leffler (Jonathan.Leffler@Informix.com) #include <disclaimer.h> > Guardian of DBD::Informix v1.00.PC1 -- http://www.perl.com/CPAN > "I don't suffer from insanity; I enjoy every minute of it!" -- Emmanuel Soden - es@4js.com Four J's Development Tools As an old man said ... If it happens once, it's a bug. If it happens twice, it's a feature. If it happens more than twice, it's a design philosophy.....