similar to: Samba 3.x and PCNetLink domain trusts

Except that everything isn't fine, because I can't login to the samba domain as a PCNL/NT4 user or vice versa. -------- Forwarded Message -------- > From: Volker Lendecke <Volker.Lendecke@SerNet.DE> > Reply-To: Volker.Lendecke@SerNet.DE > To: Damian Lock (SSCI) <Damian.Lock@ssci.com> > Cc: samba@lists.samba.org > Subject: Re: [Samba] Samba 3.x and PCNetLink

It looks as if 2-way trusts are working between Samba and PCNL and between Samba/NT4. The one exception seems to be logging in as Samba/myname on the ENT4 PDC. I had created a ENT4/myname account. I had forgotten to add SAMBA/myname to the local users group on the ENT4 PDC before trying to the ENT4 PDC as SAMBA/myname. If I log in as SAMBA/anothername it is OK. This isn't real show

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

I found part of the prob may have been that I didn't join the samba PDC to its own domain. # net join samba -U root Joined domain SAMBA Now, commands like "wbinfo -t" and "wbinfo -m" indicate that the domains are trusted. Also, I can run "net rpc samdump" to dump the NT4 domain info (but not the PCNL domain.) If I try to log in to the NT4 server as a

I have setup a Samba 3.024 server on Solaris. I have successfully enabled two-way trusts between my samba domain and my legacy PC Netlink domain. (PC Netlink is the solaris port of NT4 aka Advanced Server for Unix.) My Samba domain includes 2 Windows 2003 Servers (One is Windows 2003 SP1, the other is Windows 2003 R2 SP2.) The PCNL server supports Windows 2000 Servers and XP Pro clients.

Thanks for the advice. I had played with NT4 a little bit to see if I could use it for setting up a resource domain for windows 2003 machines- since it looks like you can join Windows 2003 machines to an NT4 domain (so why PCNL can't I don't know), and then establish trusts between NT4 and PCNL. I didn't really want to have NT4 machines in my enviroment any longer than necessary so

I have a Sun Clutster running on two Sun Fire 4800s, OS is Solaris 9. The environment was set up with PC Netlink prior to my arrival. On Nov 24 after work I shutdown PC Netlink on both systems and started Samba. However from the windows side we can only see one Sun box and the one sun development box that I tested on prior to this weekend. The other production system can't be seen from

I have a Solaris 8 box with very old Samba 2.2.8a. It would be very convenient to join a Windows Domain with a 2003 R2 DC. (saving about 1 month of bureaucratic busy work - replacing the server) I've followed the docs on joining a Windows 2K AD, but no success: [root at box samba-2.2.8a]# smbpasswd -D 2 -j FOO -U me added interface ip=10.1.4.31 bcast=10.1.5.255 nmask=255.255.254.0

Sun PCNetlink is a NT4.0 PDC emulator. I'm running samba-3.0.13, joined to an ADS server that has a trust with a PCNetlink domain. My samba can authenticate fine against ADS accounts, but refuses to authenticate against the PCNetlink domain. I can do getent passwd "ADSDOM\user" and get an ADS user printed out, but if I use getent passwd "NT4DOM\user" nothing

As per earlier post, I was having problems getting trusts setup between my Samba domain (3.0.x PDC, 3.4.x BDC on Solaris 10) and two Active Directory domains (each in a separate forest.) One domain is a test Win 2003 PDC in native Win 2003 mode, the other is a Win 2008 system also in native Win 2003 mode. To summarize some of the progess- things work better if the Samba 3.4 is the PDC,

R version: 2.001 OS: Windows XP SP2 When I use the interp.surface() function, on occasion I have encountered the following error message: Error in interp.surface(a, loc) : subscript out of bounds Since it is somewhat dependent on the data set, I cannot say exactly in which cases these occur, but I believe I have found the problem and a solution for it: The scaling calculations in the code,

I have started tinkering with samba 4. I have a Windows 2008 active directory domain controller. It is also the main DNS server but is not the wins server. The DNS server does NOT allow DNS registration by client machines. I have a fedora core 19 linux machine with samba 4.1.13 (bundled with Fedora.) smb.conf includes security = ads realm = MYDOMAIN.COM

I now have one PDC (Samba 3.026a on Solaris 10) and several member servers (including Samba 3.026a on Solaris 9 and 10, and Samba 3.024 on Fedora core 6.) Each machine uses NIS for unix accounts. If I start smbd and nmbd on a member server, I can connect to a share from a windows 2000 or XP client. If I look at the permissions on a folder, if shows "Unix Account/someuser" or

Looking for a poniter in the right direction My current configuration is NT4 PDC (Solaris PCnetlink) Samba Member server (Solaris 9 Samba ver 3.0.20b)for file and print sharing WinXp Pro Clients SP2 My problem is with the Domain Users. I am able to share out file systems to the XP clients from my Samba server OK. I am also able to modify the permissions for the files in the share in Solaris

a separate partition Reply-To: Csillag Kristof <kristof.csillag@ge.com>, 397758@bugs.debian.org Resent-From: Csillag Kristof <kristof.csillag@ge.com> Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org> Resent-Date: Thu, 09 Nov 2006 09:33:19 +0000 Resent-Message-ID: <handler.397758.B.11630647553439@bugs.debian.org>

Hi all, I have a problem during the lauching of my first virtual image. First thing : domain 0 is on fedora core 6 (probably a xen package made in fedora :-S, sorry ...) Second thing : the error is really traditional (i already had it with uml) but there i am blocking. here my config file (for image on logical volume, swap too) root = "/dev/sda1 ro" [root@p-virtvip8 xen]# cat p-virtser9

Recently I wrote about this problem, but it still exist and I can't dial my Xlite SIP Phone So here is the Notice Jul 5 17:14:07 NOTICE[65541]: chan_sip.c:6731 handle_request: Registration from 'Damian Minkov <sip:damian@10.1.1.2>' failed for '10.1.1.11' The * box(10.1.1.2) and the PC(10.1.1.11) on which is the XLite are in the same network Here is part from sip

I have * box on machine with external ip address and internal one I'm tring to register to it from to machines - one from innternet ( everything is ok - in sip.conf nat=yes)\ and the other one is in the internal network (in sip.conf - nat=no ) and it say 403 Forbidden? Any Ideas ? here are the logs and configs From the external SIP Client whic registers.

Hello dear members of R-help and R-core mailing list, I am not sure if this request is a "ticket" that should be filled somewhere outside the mailing list. If so, I apologize for not doing and would like to know where I should have filled it. And to the subject matter: I would like to use a command like this: plot(c(1,8), 1:2, type="n") polygon(1:7, c(2,1,2,NA,2,1,2),