Server 2008 member server in a 2000 Active DIrectory Domain frequent UNC share disconnects to 2008 server

Hello,

We've set up a Windows 2008 server as a member server in a 2000 domain which
is our DMZ. It is functioning as our web server.

The name of the DMZ domain is DMZ answering to (*.*.com)

We've set up shares for users in that 2000 (AD) domain to access for the
purpose of mapping to the shares to remotely update files, etc. They use
UNC mappings to connect to these share.

Intermittently, established connections are lost from uses in the ad domain
(typically xp users) and when we try to reconnect them, we are unable to
find the Windows 2008 server (name) for a "UNC" connection. We can ping
the name and the IP address but can't connect for a UNC.

All users log on to their primary 2003 domain, let's say AD. Then they map
to the share in the DMZ, which is a 2000 AD domain called DMZ. They are
challenged for their DMZ domain username and password, which they supply.
The mapping is then successful. Sometimes it goes away on its own, or it
will go away if someone else tries to make a connection to the same share.
The second person will connect, and the first person gets disconnected.
Sometimes a person will disconnect on their own.

We have another 2000 member server in this DMZ that used to be our web
server and it has shares that users can map to fine with no issues. It is
only with the 2008 server.



Any help will be greatly appreciated!!!!!





Thanks



Gene

Have you configured the server with the file services role?

In the Networking and Sharing center, is file sharing turned on?


--
Mark Parris
MCSE: NT4.0, 2000, 2003
MCITP: EA, SA

Founder: [ADUG] UK Active Directory User Group http://adug.co.uk

"Little Help Please..." <22geno22@community.nospam> wrote in message
news:elsyksRnJHA.1288@TK2MSFTNGP02.phx.gbl...
> Hello,
>
> We've set up a Windows 2008 server as a member server in a 2000 domain
> which is our DMZ. It is functioning as our web server.
>
> The name of the DMZ domain is DMZ answering to (*.*.com)
>
> We've set up shares for users in that 2000 (AD) domain to access for the
> purpose of mapping to the shares to remotely update files, etc. They use
> UNC mappings to connect to these share.
>
> Intermittently, established connections are lost from uses in the ad
> domain (typically xp users) and when we try to reconnect them, we are
> unable to find the Windows 2008 server (name) for a "UNC" connection. We
> can ping the name and the IP address but can't connect for a UNC.
>
> All users log on to their primary 2003 domain, let's say AD. Then they
> map to the share in the DMZ, which is a 2000 AD domain called DMZ. They
> are challenged for their DMZ domain username and password, which they
> supply. The mapping is then successful. Sometimes it goes away on its
> own, or it will go away if someone else tries to make a connection to the
> same share. The second person will connect, and the first person gets
> disconnected. Sometimes a person will disconnect on their own.
>
> We have another 2000 member server in this DMZ that used to be our web
> server and it has shares that users can map to fine with no issues. It is
> only with the 2008 server.
>
>
>
> Any help will be greatly appreciated!!!!!
>
>
>
>
>
> Thanks
>
>
>
> Gene
>
>

Thanks for the reply.

I have a little more info to clarify. And yes File Sharing is turned on as
we do get connections, sometimes.


Have users in an 2003 AD domain that connect to a 2008 member server in a
2000 AD domain. There are no trusts between the domains. When they UNC
map, they use their credentials in the 2000 AD domain, ie dmz\bill.smith
than a password when connecting to share.

Sometimes it works.
Sometimes they don't even connect to the share.
Sometimes when connected, they will suddenly get disconnected for no reason.

Really weird.

Have a 2003 Server in the same 2000 AD domain, and file connections from the
2003 AD domain to the shares on that box using their 2000 AD domain
credentials work fine.

Had the same issue before when we tried another 2008 server and had to back
it down to 2003. It has to do something with 2008.

Any help.

Thanks

Gene
"Mark Parris [ADUG]" <info@adug.co.uk> wrote in message
news:u3ztmzWnJHA.5228@TK2MSFTNGP02.phx.gbl...
> Have you configured the server with the file services role?
>
> In the Networking and Sharing center, is file sharing turned on?
>
>
> --
> Mark Parris
> MCSE: NT4.0, 2000, 2003
> MCITP: EA, SA
>
> Founder: [ADUG] UK Active Directory User Group http://adug.co.uk
>
> "Little Help Please..." <22geno22@community.nospam> wrote in message
> news:elsyksRnJHA.1288@TK2MSFTNGP02.phx.gbl...
>> Hello,
>>
>> We've set up a Windows 2008 server as a member server in a 2000 domain
>> which is our DMZ. It is functioning as our web server.
>>
>> The name of the DMZ domain is DMZ answering to (*.*.com)
>>
>> We've set up shares for users in that 2000 (AD) domain to access for the
>> purpose of mapping to the shares to remotely update files, etc. They use
>> UNC mappings to connect to these share.
>>
>> Intermittently, established connections are lost from uses in the ad
>> domain (typically xp users) and when we try to reconnect them, we are
>> unable to find the Windows 2008 server (name) for a "UNC" connection.
>> We can ping the name and the IP address but can't connect for a UNC.
>>
>> All users log on to their primary 2003 domain, let's say AD. Then they
>> map to the share in the DMZ, which is a 2000 AD domain called DMZ. They
>> are challenged for their DMZ domain username and password, which they
>> supply. The mapping is then successful. Sometimes it goes away on its
>> own, or it will go away if someone else tries to make a connection to the
>> same share. The second person will connect, and the first person gets
>> disconnected. Sometimes a person will disconnect on their own.
>>
>> We have another 2000 member server in this DMZ that used to be our web
>> server and it has shares that users can map to fine with no issues. It
>> is only with the 2008 server.
>>
>>
>>
>> Any help will be greatly appreciated!!!!!
>>
>>
>>
>>
>>
>> Thanks
>>
>>
>>
>> Gene
>>
>>
>
>