Disappearing Shares

I just replaced an NT4 Server with a 2003 sp1 Server. I created a new AD tree
using w2k compatability. I joined this domain with half of the computers last
night, migrated the XP profiles ans all was fine when I left. Came in this
morning and none of those stations could see the server shares. If I
attempted to browse the nethood and look I was prompted for a user/pass for
the server. Of course if I used the admin credentials it would connect and I
coulsd get to the info. Well after pulling my hair out I decided to go ahead
and move the rest of the stations to the new domain and migrate the profiles.
Everything worked fine but after about 15 minutes they where doing the same
thing. Any idea what is causing this? I checked and the workstaions display
the correct domain under Ipconfig. It's as if I',m authenticated on the
domain but not the server. Thanks

Hi,

Can you give us a bit more information? Here are few questions that might
help...
* Are there any errors in Event logs on the server or on the client PCs?
* How is DNS set up? Is Windows 2003 server DNS server? Where do clients
point for DNS?
* How did you join the clients to new domain?

--
Mike
Microsoft MVP - Windows Security

"danb" <(E-Mail Removed)> wrote in message
news:F5355F34-6D88-4A54-A9C4-(E-Mail Removed)...
>I just replaced an NT4 Server with a 2003 sp1 Server. I created a new AD
>tree
> using w2k compatability. I joined this domain with half of the computers
> last
> night, migrated the XP profiles ans all was fine when I left. Came in this
> morning and none of those stations could see the server shares. If I
> attempted to browse the nethood and look I was prompted for a user/pass
> for
> the server. Of course if I used the admin credentials it would connect and
> I
> coulsd get to the info. Well after pulling my hair out I decided to go
> ahead
> and move the rest of the stations to the new domain and migrate the
> profiles.
> Everything worked fine but after about 15 minutes they where doing the
> same
> thing. Any idea what is causing this? I checked and the workstaions
> display
> the correct domain under Ipconfig. It's as if I',m authenticated on the
> domain but not the server. Thanks

Thanks!

No errors in the event logs on the server; didn't think to look on the
workstations.

Server is the DNS server. However, after making my post and finding a
related incident (which somwhow eluded me for 3 hours of research yesterday)
I am going to go and revisit this issue. The server is not a DHCP server and
the workstations are getting DHCP from the IDSL router. I checked the DNS
info on a machine that was still working I think.

I joined the clients by changing the domain name in XP. That all went normal.

In the future, people with this type of problem should limit there searches
to the word 'shares' ! If you have any ideas I would love to hear them.
Thanks for your reply. I will let you know what (if anything) I come up with

Dan

"Miha Pihler [MVP]" wrote:

> Hi,
>
> Can you give us a bit more information? Here are few questions that might
> help...
> * Are there any errors in Event logs on the server or on the client PCs?
> * How is DNS set up? Is Windows 2003 server DNS server? Where do clients
> point for DNS?
> * How did you join the clients to new domain?
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "danb" <(E-Mail Removed)> wrote in message
> news:F5355F34-6D88-4A54-A9C4-(E-Mail Removed)...
> >I just replaced an NT4 Server with a 2003 sp1 Server. I created a new AD
> >tree
> > using w2k compatability. I joined this domain with half of the computers
> > last
> > night, migrated the XP profiles ans all was fine when I left. Came in this
> > morning and none of those stations could see the server shares. If I
> > attempted to browse the nethood and look I was prompted for a user/pass
> > for
> > the server. Of course if I used the admin credentials it would connect and
> > I
> > coulsd get to the info. Well after pulling my hair out I decided to go
> > ahead
> > and move the rest of the stations to the new domain and migrate the
> > profiles.
> > Everything worked fine but after about 15 minutes they where doing the
> > same
> > thing. Any idea what is causing this? I checked and the workstaions
> > display
> > the correct domain under Ipconfig. It's as if I',m authenticated on the
> > domain but not the server. Thanks
>
>
>

I dosconnected the IDSL router, built the DHCP in 2003 server, released and
renewed all the clients and everything went great...except.after connecting
the router back up, I discovered I an't resolve domain names for internet
access.

Any ideas?

V/R, Dan



"danb" wrote:

> Thanks!
>
> No errors in the event logs on the server; didn't think to look on the
> workstations.
>
> Server is the DNS server. However, after making my post and finding a
> related incident (which somwhow eluded me for 3 hours of research yesterday)
> I am going to go and revisit this issue. The server is not a DHCP server and
> the workstations are getting DHCP from the IDSL router. I checked the DNS
> info on a machine that was still working I think.
>
> I joined the clients by changing the domain name in XP. That all went normal.
>
> In the future, people with this type of problem should limit there searches
> to the word 'shares' ! If you have any ideas I would love to hear them.
> Thanks for your reply. I will let you know what (if anything) I come up with
>
> Dan
>
> "Miha Pihler [MVP]" wrote:
>
> > Hi,
> >
> > Can you give us a bit more information? Here are few questions that might
> > help...
> > * Are there any errors in Event logs on the server or on the client PCs?
> > * How is DNS set up? Is Windows 2003 server DNS server? Where do clients
> > point for DNS?
> > * How did you join the clients to new domain?
> >
> > --
> > Mike
> > Microsoft MVP - Windows Security
> >
> > "danb" <(E-Mail Removed)> wrote in message
> > news:F5355F34-6D88-4A54-A9C4-(E-Mail Removed)...
> > >I just replaced an NT4 Server with a 2003 sp1 Server. I created a new AD
> > >tree
> > > using w2k compatability. I joined this domain with half of the computers
> > > last
> > > night, migrated the XP profiles ans all was fine when I left. Came in this
> > > morning and none of those stations could see the server shares. If I
> > > attempted to browse the nethood and look I was prompted for a user/pass
> > > for
> > > the server. Of course if I used the admin credentials it would connect and
> > > I
> > > coulsd get to the info. Well after pulling my hair out I decided to go
> > > ahead
> > > and move the rest of the stations to the new domain and migrate the
> > > profiles.
> > > Everything worked fine but after about 15 minutes they where doing the
> > > same
> > > thing. Any idea what is causing this? I checked and the workstaions
> > > display
> > > the correct domain under Ipconfig. It's as if I',m authenticated on the
> > > domain but not the server. Thanks
> >
> >
> >

OK it is all working. I forgot to add the ISP DNS servers to the DHCP server.

Thanks for all your help- Dan

"danb" wrote:

> I just replaced an NT4 Server with a 2003 sp1 Server. I created a new AD tree
> using w2k compatability. I joined this domain with half of the computers last
> night, migrated the XP profiles ans all was fine when I left. Came in this
> morning and none of those stations could see the server shares. If I
> attempted to browse the nethood and look I was prompted for a user/pass for
> the server. Of course if I used the admin credentials it would connect and I
> coulsd get to the info. Well after pulling my hair out I decided to go ahead
> and move the rest of the stations to the new domain and migrate the profiles.
> Everything worked fine but after about 15 minutes they where doing the same
> thing. Any idea what is causing this? I checked and the workstaions display
> the correct domain under Ipconfig. It's as if I',m authenticated on the
> domain but not the server. Thanks

Hi,

Clients should only have your internal DNS (e.g. your Active Directory DNS
server). On your DNS server (where clients point to) you should configure
Forwarders which should point to your ISP.

This way, clients will be able to find domain controllers, global catalogs
in your domain and other services while they will be able to resolve
internet addresses.

If clients will have your ISP DNS set then they will not be able to find
domain controllers and will start misbehaving and in the end they will stop
working properly since they will not be able to talk to DC.

--
Mike
Microsoft MVP - Windows Security

"danb" <(E-Mail Removed)> wrote in message
news:BB6D0B26-A568-47E6-B71F-(E-Mail Removed)...
> OK it is all working. I forgot to add the ISP DNS servers to the DHCP
> server.
>
> Thanks for all your help- Dan
>
> "danb" wrote:
>
>> I just replaced an NT4 Server with a 2003 sp1 Server. I created a new AD
>> tree
>> using w2k compatability. I joined this domain with half of the computers
>> last
>> night, migrated the XP profiles ans all was fine when I left. Came in
>> this
>> morning and none of those stations could see the server shares. If I
>> attempted to browse the nethood and look I was prompted for a user/pass
>> for
>> the server. Of course if I used the admin credentials it would connect
>> and I
>> coulsd get to the info. Well after pulling my hair out I decided to go
>> ahead
>> and move the rest of the stations to the new domain and migrate the
>> profiles.
>> Everything worked fine but after about 15 minutes they where doing the
>> same
>> thing. Any idea what is causing this? I checked and the workstaions
>> display
>> the correct domain under Ipconfig. It's as if I',m authenticated on the
>> domain but not the server. Thanks