Hi Scott,
Scott Parks wrote in a message to all:
 SP> The first real problem was with TCP/IP.  I created an autoexec.ncf
 SP> similar to the 3.11 machines ... but now INETCFG REM's out the Load
 SP> and Bind statements and refers to another NCF in ETC directory. It
 SP> did not accept my Bind command for IP, did not REM it out .. and
 SP> now when I try to add TCP/IP from the Console in INETCFG it won't.
 SP> 802.3 is working fine.
There's no need to add/change protocols manually in INW (actually NW 4.x). 
After running inetcfg for the first time, the new configuration is stored in 
sys:etc\netinfo.cfg and at startup configuration is loaded using the 
initsys.ncf file from autoexec.ncf.
You have to configure TCP/IP first, using the option "Protocols" then bind 
TCP/IP to a network card using "Bindings". You will have to use Ethernet II 
or SNAP to bind this protocol, 802.x won't work. 
 SP> Is the purpose of Netsync3/Netsync4 (I think those are the names)
 SP> to allow the 3.11 servers to be added as objects to the current
 SP> tree or can they be added?  Or are they only for migration?
You can add NW 3 servers and its users to the NDs using NetSync. But this 
utilityy is for temporary use only. You should use it when migrating to NW 4 
and want to do all administrative work with NDS utilities and discard all 
bindery tools.
 SP> Also, how many patches are there for NW4.11 at this point?  I'm not
 SP> too interested in the Internet features yet.  I hope patches are
 SP> still a matter of just replacing files rather than the MS style.
IWSP4A.EXE is the main service pack for 4.11, replacing a lot of NLMs and has 
a size of >10 MB. 
           Bernd 
---
---------------