Re: Windows drive mapping to IFS; DNS Nope, IP address Yes

[Dan <dan27649@xxxxxxxxx>]

We have been on v7r1 since I started here two years ago.

I use i Access for Windows 7.1 and RDi 9.6, both of which connect to the i
via DNS name.

Pinging by DNS name works, and it correctly idenitifies the IP address of
the server.  Pinging by IP address works as well.

The local hosts file on my PC (at C:\Windows\System32\drivers\etc\) has one
entry:
127.0.0.1    Mitel_Teleworker

While I'm in that folder, the "networks" file has one entry:
loopback                 127

Nav for i / Netserver shows no disabled user IDs.  The system name
matches.  Nothing stands out in any of the tabs under Properties. FWIW,
"Allow IBM i NetServer access using the system name: Yes".  I see a few
entries in Sessions that has my user ID.  Nothing unusual under Status.

- Dan

On Wed, Apr 11, 2018 at 1:39 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

> What version of IBM i are you running?  If you've upgraded to 7.3 then you
> may be noticing the SMB2 issue.  This is best cured by putting on the
> latest Windows fix packs.  In your case it would also involve upgrading to
> Windows 10.  For more information check out
> https://wiki.midrange.com/index.php/OS_Upgrades
>
> Now, I wouldn't think it would matter IP address vs dns.  Can you ping the
> system by that name?  You might want to see if the IP address changed and
> you have an old host table entry on your PC.  Host table entries are often
> the root of all evil.  You might also want to check and find out what DNS
> servers your PC uses and see if that list is current.
>
> You also might want to verify your IBM i's NetServer properties.  This
> involves poking around at http://youribmi:2001.  Verify the system name,
> and the domain name, are correct.