AS400 name not resolving in DNS

pts.
Tags:
AS/400
PC/Windows Connectivity
On Sunday I restarted my AS400 prior to doing my monthly full system back up. When it came on line, none of my PC's could resolve the system name (s10a####) to the internal ip address. I entered a DNS entry manually on my internal Windows 2003 DNS server, and all the PC's running XP pro can connect fine, but the PC's running Win98 still don't see it. I reconfigured them to connect to the ip instead of the name in the connection manager, but I was wondering if anyone knew why this could have happened? Could something not have restarted during the re-ipl of the As400? There is no messages in the log, and no indications of trouble. This isn't urgent since I found a workaround using the static ip, but I hate to have something change and not know why.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hi

Not sure why this would happen after an IPL. I have had occasions where networking with Windows 98 has stopped behaving itself and I’ve had to install additional network protocols to rectify the situation. My guess would be it’s probably coincidence with the IPL.

For Windows 98 I have always had to add the local systems into the “hosts” file in C:WindowsSystem32. This acts as a local DNS file for Windows and I would suggest you check that the System name is in there correctly.

All the best

Jonathan

===========================================================

Since you don’t tell us what OS version/release you’re running nor how your interfaces are defined on your AS/400 nor what your domain configuration is on your AS/400 nor what entry you added to the DNA other than “s10a####” which is almost certainly wrong, it’s hard to guess.

Tom

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • KasMcc
    We have some Win98 PCs attached using iseries access v5.3 and found that we had to make sure the name of the AS400 was present in both the Hosts and LMhosts files for these PCs to connect.
    230 pointsBadges:
    report
  • Dalejanus
    If your network is peer to peer, one pc is assigned as the browsemaster computer, where the others get the names you see in network neighborhood, etc. What computer is assigned as browsemaster is an arcane windows mystery, but perhaps it was offline at the time of your ipl. It can also take up to 15 minutes to recognize a new computer added to the network. You mentionedyou are running internal DNS server, so perhaps this is not the problem. I'm not up on win98, but as others have pointed out, WIN98 uses a HOST file to convert ip addresses to names. Are you using one? Do you have that internal DNS ip address assigned to the network protocol on the win98 computers? I use my DSL providers DNS address, which worked fine until they changed it without telling anyone. No one could browse the internet until I changed all the network configurations to the new DNS address. It was very 'exciting' around here before I figured out it was a DNS problem. I only have 1 win98 left, and my enviroment is very static . All I can point out are some things that have bitten me in the past.
    0 pointsBadges:
    report
  • Sidzilla
    Some more details: I am running Windows 2003 and Windows 2000 servers, using active directory on them, I have a 2003 server set up as an internal DNS server, and up until the AS400 cycled the Windows 98 machines connected flawlessly, so while I am going to check the Host files, I don't really suspect them of being the problem. I am inclined to agree that it was more than likely a coincidence and the problem lies not with the as400 but with my DNS set up. Microsoft updates were applied since the last ipl.
    0 pointsBadges:
    report
  • Nick01
    WIN 2003 DNS likes long DNS names. CA400 uses short. DNS creates a temporary entry for a period trying to make a long name from your short name. This will eventually get cleared from the DNS db but be still be in use on the network until you IPL. Then blamo, no connection Had same problem with FTP jobs we run using our short host name.
    0 pointsBadges:
    report
  • Sidzilla
    Thanks! I can finally make sense of what happened!
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following