Problems with Permissions



Applies to: Small Business Server 2003 & Windows XP Professional w/SP3

Hi everyone,
I wonder if someone may be able to help with a Permissions issue I have, I've got one SBS2003 machine up and running, and to the best of my ability configured correctly, I've added a Windows XP Pro machine to the computers and created an account for myself with Administrator privileges, on both the SBS and XP machine I have shared certain folders and included my account in the Security with full permissions, from the XP box if I go to My Network Places I can create a new network place using those shared folders from the SBS box, but if I try to do the same from the SBS box by creating a network place to a shared folder on the XP machine, I get an error message saying the network path cannot be found or I don't have permission to access it.

I'm at a loss as to what I may be doing wrong because clearly my user account is configured in Active Directory as I can log on to the Windows XP machine using the credentials that I created in AD. Just for clarity the SBS box is also a Domain Controller if that makes any difference.

Can anyone see something obvious that I may be overlooking?

Any help, pointers or suggestions would be greatly appreciated.

Kind Regards,
Wayne


Relevant Pages

  • Re: Windows Update after SP2 installation
    ... that is one of the dll registration entries that was in my ... Microsoft MVP - Windows Shell/User ... > pointers, hr=80040154 ...
    (microsoft.public.windowsupdate)
  • (null)
    ... to printf or similar API. ... maybe when someone decided that some abuses of null pointers were less ... Does a Windows XP API do the same thing? ...
    (microsoft.public.development.device.drivers)
  • Re: Ranting about JVMs default memory limits...
    ... Originally, 32-bit Windows split it half and half, with the user code getting 2GB and the OS getting 2GB. ... But, the OS didn't really need 2GB of address space, and so enabling "LARGEADDRESSAWARE" tells the OS that the application doesn't make any assumptions about the range of pointers and that it can pass user data addresses to the process in the first 1GB of the second 2GB of the full 4GB address space. ... Memory blocks aren't moveable, so allocations can sit in between two free blocks, limiting the size of the largest block that can actually be allocated. ... Depending on the allocation pattern, it's not hard at all to have over 1GB of virtual address space left, but not be able to allocate any single block nearly that large. ...
    (comp.lang.java.programmer)
  • Re: About Windows address space
    ... > Is there any minimum value for pointers, that is consistent across all ... This must include all pointers a user-space program ... be difficult to differentiate from a string pointer, ... Windows does it by limiting handles that can also be strings to a maximum ...
    (alt.lang.asm)
  • Re: COLOR CHANGE OF CURSOR
    ... As I was saying, besides the mouse pointers that come with Windows, you can ... > mean the mouse pointer rather than the insertion point. ... >>> of my cursor from white to i.e. ...
    (microsoft.public.word.customization.menustoolbars)