Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
5

Does the list exists in the root of the site collection or in a sub site? If the list is in the root than you can call it with: http://yourserver:port/_vti_bin/Lists.asmx If the list you request is on a subsite you need to call the web service like this http://yourserver:port/SUBSITE/_vti_bin/Lists.asmx


4

Bill Baer outlines the required ports. If you want to test it, I created the People Picker Port Tester which you would run from the SharePoint server(s). The query is only done from the SharePoint server. End user machines do not need those ports open to the remote DCs. Ports: TCP/UDP 135, 137, 138, 139 (RPC) TCP/UDP 389 by default, customizable (LDAP) ...


2

You cannot restrict ports like that. All SharePoint servers must have access to all SQL Servers that are members of the farm.


2

Check with Configure an Alternate Access Mapping in SharePoint 2010. http://technet.microsoft.com/en-us/sharepoint/ff679917.aspx


1

Yes Public IP is a must also you have to configured your router with port forwarding to.. http://mroffice365.com/2011/10/how-to-open-a-sharepoint-2010-website-for-internet-access/ above article might help you to get this thing done.


1

I got it to work. Cross-firewall access zone wasn't set up. I just created alternated access mapping and mapped that zone to cross-firewall access zone. Thank you.


1

all sharepoint does is read AD, I'm also the system admin who installed sharepoint 2010 also on a VM for the front end server and had it create its database's on an existing MSSQL 2005 DB server. No Problems, works great actually its nice to have a intranet to ties in with AD so very well.


1

Installing SharePoint doesn't do anything to your Active Directory schema. There is also no reason to not have the VM on the network - we have multiple SharePoint development VMs that are on our domain. We remote into them (and restrict permission to each individual VM) in order to do development. Having the VM on the domain is very helpful. No need ...


1

This is a quick devop hack to your complex scenario: Have the developers connect to a remote session on the VM based on logon accounts from the VMs isolated Active Directory. Get all the dev tools on the VM and they should be good. To avoid interruptions from application pool resets have them work on different Web Applications.


Only top voted, non community-wiki answers of a minimum length are eligible