We are running a Windows NT network and have two WINS servers (we are not
running DNS). We also have four AS/400's on our network as well. All of
our client PC's are running "IBM Client Access" for 5250 sessions to the
AS/400. I have a user trying to use the "Remote Procedure Command" to run a
command on a PC. They reference the PC by it's Windows NetBios name. Of
course the AS/400 can't find the PC because the AS/400 doesn't use NetBios.
Can the AS/400 be configured to reference the WINS servers for NetBios Name
Resolution? Our AS/400 is a model 170 running OS/400 V4R2. Thanks for your
help.
Lamar Thomas
Note that this setup makes DHCP a little nicer also. You just plug in a
new PC and everything can find it. If the address gets changed later,
you won't even notice.
Charles
In article <39e4a641$1...@news01.m-l.net>, lam...@aldon.com says...
Nope... but why don't you run a DNS server internally ?
I often see people "abusing" WINS servers for IP name resolution (while
they're only intended for Netbios name resolution). BTW, Microsofts WINS
server also registers its entries in the DNS server so this is really a nice
setup.
Regards,
Paul
----------------------
Lamar Thomas wrote in message <39e4a641$1...@news01.m-l.net>...
AS/400 and WINS Name Resolution
We are running a Windows NT network and have two WINS servers (we are not
running DNS). We also have four AS/400's on our network as well. All of
our client PC's are running "IBM Client Access" for 5250 sessions to the
AS/400. I have a user trying to use the "Remote Procedure Command" to run a
command on a PC. They reference the PC by it's Windows NetBios name. Of
course the AS/400 can't find the PC because the AS/400 doesn't use NetBios.
Can the AS/400 be configured to reference the WINS servers for NetBios Name
Resolution? Our AS/400 is a model 170 running OS/400 V4R2. Thanks for your
help.
Lamar Thomas
The contents of this message express only the sender's opinion.
This message does not necessarily reflect the policy or views of
my employer, Merck & Co., Inc. All responsibility for the statements
made in this Usenet posting resides solely and completely with the
sender.
configure the new DNS in the AS/400 TCP stack and it will resove PC names
via NT DNS<--->WINS
It works fine for us.
By the way, it is a pity the lack of WINS service on the AS/400 (WINS has
it's own RFC).
"Juan Ramón García Martel" <jram...@idecnet.com> escribió en el mensaje
news:8s4616$lti$1...@diana.bcn.ttd.net...
Charles
In article <8s46ih$sjf$1...@diana.bcn.ttd.net>,
jramonga...@idecnet.com says...
I don't think the WINS server actually updates the DNS server. When you
configure the DNS server you have an option to tell it where the WINS
server is at and configure it to ask the WINS server if it doesn't have
an entry in it's tables for a particular name/IP address.
At least that's how I remember setting up our NT Server ;-)
Regardless, it is a nice setup particularly in conjunction with DHCP.
Since WINS is dynamic you end up with a Dynamic DNS (via WINS) for any
new Windows PCs. In fact this capability is one reason I left our DNS on
our NT server instead of moving it to the 400.
Charles Wilt
In article <8s3mbh$n8p$1...@merck.com>, paIulHATE_...@merck.com
says...
Michael Frilot
On Wed, 11 Oct 2000 19:32:25 GMT,
charle...@worldnet.no.spam.att.net (Charles Wilt) wrote:
>I'm pretty sure the answer to that is no. What you need to do is
>configure a DNS server that will pass requests to your WINS server(s).
>The DNS server M$ provides with NT can be configured this way. I don't
>know for sure if the DNS on the 400 will do this, but I don't think so.
>
>Note that this setup makes DHCP a little nicer also. You just plug in a
>new PC and everything can find it. If the address gets changed later,
>you won't even notice.
>
>Charles
>
>
>
>In article <39e4a641$1...@news01.m-l.net>, lam...@aldon.com says...
The problem is that TCP/IP doesn't know anything about WINS, thus
commands like PING, RUNRMTCMD ect. use DNS to find the named system.
Netserver on the other hand, does know WINS. So I would imagine that you
could successfully access files via /QNTC/PCSERVERNAME/... even if that
PCSERVERNAME isn't in the DNS.
HTH,
Charles
In article <39e5f6ac....@remotenews.virginia.edu>,
michael...@heiligmeyers.com says...
The WINS tab allows you to activate a WINS proxy function. This allows
you to use your AS/400 as a kind of gateway to a real WINS server. You
might have PCs attached to your AS/400 that do not have a network
connection to your WINS server. By activating the proxy function, the
AS/400 will relay WINS resolution requests between those PCs and the
WINS server.
When needed, this is certainly a handy function. But it can also
overwhelm your network when the feature is activated unnecessarily in
an inappropriate environment.
These comments based on interpretation of painful experience rather than
direct training. I'm no WINS expert.
Tom Liotta
In article <39e5f6ac....@remotenews.virginia.edu>,
--
Tom Liotta, AS/400 Systems Programmer
The PowerTech Group, Inc.; http://www.400security.com
...and for you automated email spammers out there:
rhu...@fcc.gov jqu...@fcc.gov sn...@fcc.gov rch...@fcc.gov
Sent via Deja.com http://www.deja.com/
Before you buy.
You're correct... I expressed it incorrect (it's the DNS server that queries
WINS, not WINS inserting entries in the DNS).
Regarding your other post of not needing a WINS server on AS/400... we've
several customers that are pure AS/400 shops and use NetServer for file
sharing, however due to their network setup (ie. multiple subnets) nobody
sees the AS/400 in his network neighborhood.... a WINS server solves this
issue.
Having WINS on AS/400 wouldn't require us to bring in NT Servers at those
companies.
Kind regards,
Paul
-----------------
Charles Wilt wrote in message ...
Paul,
I don't think the WINS server actually updates the DNS server. When you
configure the DNS server you have an option to tell it where the WINS
server is at and configure it to ask the WINS server if it doesn't have
an entry in it's tables for a particular name/IP address.
At least that's how I remember setting up our NT Server ;-)
Regardless, it is a nice setup particularly in conjunction with DHCP.
Since WINS is dynamic you end up with a Dynamic DNS (via WINS) for any
new Windows PCs. In fact this capability is one reason I left our DNS on
our NT server instead of moving it to the 400.
Charles Wilt
In article <8s3mbh$n8p$1...@merck.com>, paIulHATE_...@merck.com
says...
> Hi Lamar,
>
> Nope... but why don't you run a DNS server internally ?
>
> I often see people "abusing" WINS servers for IP name resolution (while
> they're only intended for Netbios name resolution). BTW, Microsofts WINS
> server also registers its entries in the DNS server so this is really a
nice
> setup.
>
> Regards,
> Paul
The contents of this message express only the sender's opinion.
Well, none of them are pressent in OS/400 ....
The fact that both NT WINS and DNS talk with each other makes an NT server
indispensable .....
Why not implement it on AS/400 (or should I say Eserver Iseries 400 ??? What
a name! ;) and get rid of NTs jungle ?
I can see why having a WINS server on the 400 might be useful in those
cases. However, IMHO until the 400 could handle all the duties of an NT
server, it makes sense to have at least one NT server as PDC. This may
not apply on smaller Win 9x/ME networks, but for larger NT/2000 networks
I feel that user management is easier with the NT server in place.
I could be wrong but I don't see IBM adding PDC capabilities to the 400
anytime soon.
Another plus to having the NT server, there's a lot of stuff on mine that
I want to save but that isn't critical to our business. NT DASD is a
heck of a lot cheaper than 400 DASD.
Charles
In article <8s6bdr$gas$1...@merck.com>, paIulHATE_...@merck.com
says...
> > Hi Lamar,
> >
> > Nope... but why don't you run a DNS server internally ?
> >
> > I often see people "abusing" WINS servers for IP name resolution (while
> > they're only intended for Netbios name resolution). BTW, Microsofts WINS
> > server also registers its entries in the DNS server so this is really a
> nice
> > setup.
> >
> > Regards,
> > Paul
>
>
>
>
>
In particular he needs a DNS that talks to WINS, thus I agree that
currently an NT server is indispensable.
However, see the my latest post to Paul about why adding WINS to the 400
wouldn't be an answer.
Charles
In article <8s6go8$ais$1...@diana.bcn.ttd.net>,
jramonga...@idecnet.com says...