Re: drive not mapped because no network found

This might sound a little odd, but on your remote pc, have you tried going ..

... Start, Search,  Search files & Folders

... when that comes up you have an option to search for other computers, click 
that
... then put in the ip address of your iseries
... this has worked for me when other things have failed before
... it's worth a shot
... if this finds it, then go ahead and map it.
..... it shouldn't be a problem after that

I'm going out of town this morning, will see if this worked on Monday
... good luck

.... It may also be that Bell South is going to have to provide more support

Terry N
  ----- Original Message ----- 
  From: Jim Franz<mailto:franz400@xxxxxxxxxxxx> 
  To: Midrange Systems Technical Discussion<mailto:midrange-l@xxxxxxxxxxxx> 
  Sent: Friday, June 10, 2005 4:56 AM
  Subject: Re: drive not mapped because no network found


  >is the Iseries Netserver started ... that gets you to the ifs

  Yes - local users still having no problem mapping a drive.
  I can remotely see IFS thru OpsNav and can browse thru the files.
  While connected via Cisco VPN client to the router in the office,
  I am using the same \\qs10077xx\xxxxxxx<file://qs10077xx/xxxxxxx>   share 
name the local users use.
  I do think my WinXP desktop needs the netbios traffic the Cisco Client
  is not supporting.
  btw-this whole problem started when BellSouth's sales & tech people
  said "your remote vpn access will connect you to your local lan as if
  you were a local user..." They know not of what they speak. This is
  only another chapter in a long saga.
  jim

  ----- Original Message ----- 
  From: "Terry" 
<tnonamaker@xxxxxxxxxxxxxxxx<mailto:tnonamaker@xxxxxxxxxxxxxxxx>>
  To: "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>>
  Sent: Thursday, June 09, 2005 11:47 PM
  Subject: Re: drive not mapped because no network found


  Client access goes thru the telnet server

  is the Iseries Netserver started ... that gets you to the ifs
    ----- Original Message ----- 
    From: Jim Franz<mailto:franz400@xxxxxxxxxxxx<mailto:franz400@xxxxxxxxxxxx>>
    To: 
MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>>
    Sent: Thursday, June 09, 2005 7:59 PM
    Subject: drive not mapped because no network found


    I get this error "drive not mapped because no network found"
    from remote pc's accessing network via Cisco vpn client thru internet
    and trying to map drive in ifs directory.
    I can open Client Access & get iSeries, but not map a drive.
    Cisco help site says"
    IPSec does not encapsulate NetBIOS broadcast traffic.
    A WINS server is required to map a drive on the Microsoft network"
    We have no network server, just pc's and iSeries.
    Local pc's on lan have no problem mapping drive in ifs.
    Any ideas?
    Jim Franz
    -- 
    This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
  list
    To post a message email:
  
MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>>
    To subscribe, unsubscribe, or change list options,
    visit:
  
http://lists.midrange.com/mailman/listinfo/midrange-l<http://lists.midrange.com/mailman/listinfo/midrange-l<http://lists.midrange.com/mailman/listinfo/midrange-l<http://lists.midrange.com/mailman/listinfo/midrange-l>>
    or email:
  
MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>>
    Before posting, please take a moment to review the archives
    at
  
http://archive.midrange.com/midrange-l<http://archive.midrange.com/midrange-l<http://archive.midrange.com/midrange-l<http://archive.midrange.com/midrange-l>>.

  -- 
  This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
  To post a message email: 
MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
  To subscribe, unsubscribe, or change list options,
  visit: 
http://lists.midrange.com/mailman/listinfo/midrange-l<http://lists.midrange.com/mailman/listinfo/midrange-l>
  or email: 
MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
  Before posting, please take a moment to review the archives
  at 
http://archive.midrange.com/midrange-l<http://archive.midrange.com/midrange-l>.

  -- 
  This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
  To post a message email: 
MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
  To subscribe, unsubscribe, or change list options,
  visit: 
http://lists.midrange.com/mailman/listinfo/midrange-l<http://lists.midrange.com/mailman/listinfo/midrange-l>
  or email: 
MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
  Before posting, please take a moment to review the archives
  at 
http://archive.midrange.com/midrange-l<http://archive.midrange.com/midrange-l>.