Samba logins and IP/NetBeui (Was: The secret diary ...)
I installed Tera Term Pro on the PC and managed to TelNet to the server
Good - sounds like your basic networking is ok now.
I fiddled round with smb.conf directly and managed to get a share appearing in Networkwork neighbo(u)rhood but it doesn't seem to like my passwords...?!!!
Well, may be time to delve into the Samba books One aside, the Windows machines would typically install windows networking (SMB) onto NetBeui *and* TCP/IP as the underlying protocols. Samba only supports TCP/IP. It is possible to remove NetBeui on *all* Windows machines and the server - and just have one network protocol running on your network - ie all machines just talking IP. I am not advising this though - unless you know that you have no machines that only talk NetBeui (ie not IP) - and that all machines are configured for IP. It is something else to think about though as life can often be simpler if you only have one network protocol on your system. This is not an important point though - and if everything is working, then 'ain't broke, don't fix' probably applies ... :-) Just thought I would mention it. (even Win 3.11 can run with networking just using IP - it is not the default, and you need the Win 3.11 IP stack from MS - but on a smaller machine, cutting down to a single network protocol can save (some) resources. This is what I do at home) Kevin.
Kevin Et al Success! I seem to have a successful Samba share in WIn98. I reran the password encryption command and it worked! I still seem to have a problem with the ISDN connection. It is sometimes connecting and still looking for localhost:901 on the web. Ifconfig gives: eth0 : 192.168.1.1 192.168.1.255 255.255.255.0 IPPP0 192.168.0.99 PtP 192.168.0.1 255.255.255.255 lp 127.0.0.1 255.0.0.0 James Carter p.s to other newbies. Definitely read a couple of book before getting advice. It helps you to apply the comments and help given. Having downloaded the O'Reilly Samba manual and used Intranet Server balckbook I can recommend both in support of the SuSE manual if you use tht flavour.
I still seem to have a problem with the ISDN connection. It is sometimes connecting and still looking for localhost:901 on the web.
Couple of thoughts on this:- A major cause of dodgy ISDN calls are errant DNS/WINS lookups, look over your network setup and just have a think about this. Do you have an entry for localhost in your /etc/hosts file? You should have by default, but maybe its been broken or inadvertently commented out. Are you connecting to websites through a proxy server? It could be that your browser is going off to a proxy server on the other side of the ISDN server, even when it's meant to be connecting to itself. What make is the ISDN router and do you have access to it? You might be able to get details on the packets that are bringing up the line ( aaah, happy memories, decrypting the raw hex of an IP packet output by a 3Com OfficeConnect.... ). -- Wenn es wert das Tun ist, ist es wert das Tun falsches schnelles Sent through GMX FreeMail - http://www.gmx.net
participants (3)
-
James H. Carter & Cybèle de Jong -
kevin.taylor＠powerconv.alstom.com -
Nick Drage