Re: new server...

You'll also need to look at any TCP/IP applications to make sure they
aren't lookfor the old old domain name. Specifically, the HTTP server
and WebSphere can have problems with this change.

Matt

Dr.UgoGagliardelli wrote:
George Applegate wrote:
I am replacing an existing network server with a new one that teh
as/400 is part of, and as a result am going to have a domain name
change.

What do I need to change on teh as/400 if anything??? It will still be
at the same ip address as the old serve, and the server itself will
have the same name, but the domain name is going to be different. Is
this going to cause problems with client access on my clients or
anything else?? Just wondering what, if anything I might have to do on
the /400 side so it still works with the server and clients, or if
anything on the clients.

thanks in advance,
If the only thing to change is the tcpip domain name, just put it in
as/400 tcpip configuration entering CFGTCP command and select option 12
from the configuration menu, there's a field that holds it. Maybe you'll
need to change names held in the host table if any, that's option 10 of
the same menu. The domain name can appear in remote output queues
configuration too. To change it you can choose option 2 from the list
got by WRKOUTQ command and verify what's inside "Remote System" (RMTSYS)
field. Before changing an output queue you must stop the writer program
if any, you'll see its name in the 4th column of WRKOUTQ panel, to stop
it choose option 9 and then option 4+ F4 specifying *IMMED as
termination option.
If you changed the windows workgroup or domain name, you may want to
change it too via netserver configuration from "iseries
navigator/network/server/tcpip" or via QZLSCHSN API.
--
Dr.Ugo Gagliardelli,Modena,ItalyCertifiedUindoscrasherAñejoAlcoolInside
Spaccamaroni andate a cagare/Spammers not welcome/Spammers vão à merda
Spamers iros a la mierda/Spamers allez vous faire foutre/Spammers loop
schijten/Spammers macht Euch vom Acker/Spamerzy wypierdalac'

.

Relevant Pages

  • Re: how to access remote CUPS printer?
    ... Something on a distant network? ... and you must have port 631 tcp and udp open on the CUPS server. ... they are not automatically seen by the clients. ... I got jack of the lot of those half-arsed configuration ...
    (Fedora)
  • Re: time sync with ntp not working correctly? - solved
    ... restrict IP mask 255.255.255.255 nomodify notrap noquery ... The server: ... So the clients are not getting responses ... > unfortunately didn't shows us the ntp configuration on the two ...
    (Fedora)
  • Re: Local NTP for 5 Subnets
    ... NTP Server. ... The clients should all have the same configuration file, ... if you have all your clients talking to the server. ...
    (comp.protocols.time.ntp)
  • Re: Cups not seeing remote printer!
    ... > I have no configuration data about the printer from ... > system-config-printer on any other host. ... > file at the print.local.net server and not modifying it. ... clients should be necessary. ...
    (Fedora)
  • Problem With Internet Sharing
    ... also configured the clients the problem is the clients are not opening all ... but the clients machine is opening sify,google,railways etc websites but on ... the other hand the server is opening all the sites. ... Windows IP Configuration ...
    (microsoft.public.windowsxp.network_web)
Loading