Double checking TCP/IP

• To make absolutely sure that you can actually 'reach' the Samba server with the TCP/IP protocol, try 'pinging' it first. Let's say the IP address of the Samba server you want to access is 193.63.255.4. When you execute the command on the following line, you should get the result after it:

        [e:\tcpip\etc]ping 193.63.255.4
        PING 193.63.255.4: 56 data bytes
        64 bytes from 193.63.255.4: icmp_seq=0. time=76. ms
        64 bytes from 193.63.255.4: icmp_seq=1. time=56. ms
        64 bytes from 193.63.255.4: icmp_seq=2. time=56. ms
        ^C
        External process cancelled by a Ctrl+Break or another process
        

  If you don't get a similar output, your TCP/IP settings are incorrect. You'll have to get these working first because if you can't ping your Samba server, you never will be able to access its shares. If ping does work, try pinging the machine by its alphanumerical address, e.g. ping sunsite.doc.ic.ac.uk

• The default value for the workgroup parameter in Warp 4 and Warp Connect is IBMPEERS. However, Samba and the English versions of Windows d efault to WORKGROUP so in most cases you will want to use this instead.

• I recommend using the same NetBIOS name for your machine as the hostname under which your machine is known on the TCP/IP network (see the line SET HOSTNAME= in your CONFIG.SYS). I would not use special character such as spaces in the hostname. Also, try to keep the hostname within 8 characters.

• If you have a network with a lot of Microsoft LAN Manager clients and no NT or LAN Manager servers, you might want to use the workgroup STANDALONE. This allows the clients to start up faster.