Hi I have samba running on 3 SGI machines, mixed with a lot of PC's running Windows NT. On all my intel machine, i could see my samba (sgi) machine without any problems. But, I have a NT machine on DEC alpha 250. I can't see any samba machine, but I see all the other windows machine. I tried to run smbclient and I got a connection refuse on port 139. I got error connecting to xxx.xxx.xxx.xxx:139 (Invalid argument) When I produce verbose output I got Opening sockets Connecting to xxx.xxx.xxx.xxx at port 139 I got error connecting to xxx.xxx.xxx.xxx:139 (Invalid argument) I'm able to contact the sgi from the DEC machine via the usual TCP/IP service like telnet etc. Did I do somethings wrong, or there is a limitation with DEC alpha Thank -- ------------------------------------------------------------------------- Gaetan Lord - RTA - gaetan@sgi.com - SGI - Montreal, Canada pager: gaetan_p@montreal.sgi.com (200 car. max) "There is no future in time traveling" -------------------------------------------------------------------------
Ok, I am new to Samba (Linux in general for that matter), but I am playing around with it to see if it can be a good alternative to see if it could be a good option rather than installing a new NT server. I have printed out and read the man pages, but am still having a problem with getting it configed correctly. When I run the smbclient program and try to connect to get a list of shares from my NT server I get the following errors Get_Hostbyname: Unknown host la.de.da.com Failed to get my hostname. Get_Hostbyname: Unknown host la.de.da.com No interface found for address 196.126.10.64 Added interface ip=196.126.10.64 bcast=196.126.10.255 nmask=255.255.255.0 Get_Hostbyname: Unknown host la.de.da.com. Get_Hostbyname: Unknown host la.de.da.com. Get_Hostbyname: Unknown. host la.de.da.com Get_Hostbyname: Unknown host NTSERVER. Anyone have any ideas? Thanks. Jim jameso@shf.org
> From: Peter Blake <ppb@baloo.tcp.co.uk> > To: Johan Meiring <jjm@iname.com> > Subject: Re: Disk size on my NT > Message-ID: <Pine.BSI.3.95.980218064049.15559A-100000@ka.blake.org.uk> > > On Tue, 17 Feb 1998, Johan Meiring wrote: > > > >On Wed, 11 Feb 1998 tmh/Copenhagen@manbw.dk wrote: > > > > > >> HI Samba Admin's > > >> > > >> I have a share called "archive". The disksize on the HP is 7GB, my > > NT > > >> 3.51 and NT 4.0 says it's 4GB. > > >> > > >> Can anyone help me? > > >> > > > > > >Hi, > > > > > >W95 would report it as 2GBytes. It's a fundamental limitation of a 32-bit > > >integer: unsigned = 4 GBytes, signed = 2 GBytes. > > > > > >You will have to partition the drive to make all of it useable by the M$ > > >products. I think it might be distinctly dodgy to use it as it is.> > The corruption takes the form of source files being overwritten by output > files. The problem can be reproduced by simple PRN generator tests, so it > is not due to the video editing suite. > > Limiting the partition size to 2 GBytes greatly reduces the incidence of > file corruption - a practice recommended in M$ KnowledgeBase articles.Could this explain a long standing problem ive had with word documents randoming becoming corrupt and crashing word ?. For quite a long time I was running a 4gib home 'disk' for my users, all win95 workstations. With roving profiles on, some users just couldnt use Office97 at all. Word6 seemed ok. Ive now turned roving profiles off and the problem isnt so acute, but occasionally, some documents still crash word. Im now have a 23Gb 'home' partition. If windows simply doesnt like large server volumes, it could go a long way to explain why ive had this problem over multiple samba versions. Partitioning it up into lots of 2Gb partitions is more pain than I can contemplate. Would telling samba to 'lie' about the server volume size fix this ?