Re: DNS not working. Help!

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 07/26/04 

Date: Mon, 26 Jul 2004 13:13:17 -0400

Eugene Tan wrote:
> hi,
>
> Really stumped and wondering whether I overlooked anything or made a
> mistake.
>
> Migrated a SBS2k from old P2 to new Opteron h/w. Basically clean
> install SBS
> then migrate the data and as much settings as possible, using Exch
> Migrate Wiz
> for email and AD user accounts and roaming profiles for user
> settings. Also migrated ISA settings with ISA Tools.
>
> The main problem is DNS doesn't work/resolve outside the LAN/Domain.
> The router is ok; doing a ping to external IP works, but ping to
> domain name doesn't (hostname unknown). Ping to local PC names etc
> works.
>
> SBS has typical settings for LAN and WAN nic, and this config
> essential worked
> on the old SBS h/w. I just can't figure out what is wrong after
> looking at a few
> places. Other things are largely ok, but not having Internet is a
> real problem coz
> it also means email isn't coming in (using POP).
> Any ideas?

This can occur due to DNS misconfiguration. All servers and workstations
should specify *only* the internal AD-integrated DNS server's IP address in
their network settings. The AD-integrated DNS server should be set up with
forwarders to your ISP's DNS servers for external resolution. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202 for more
info.

>
> The other issue but not really big one is with the user profile and
> config. Perhaps
> this one shd be in some FAQ (or perhaps another thread?).
>
> In order to migrate end-user settings, I specified the user roaming
> profile folder
> in their AD User profile, in each Users' folder. Each user's
> wallpaper, layout etc
> gets copied there. PCs migrate to new SBS install by changing to
> workgroup then after reboot join the domain of new SBS (PC account).
> Then user logs in
> and the profile settings are migrated to the local 'cache' on the PC.
> Well not
> quite so simply. I found that I needed to make the users local
> administrators
> in order for their settings to be saved, otherwise even Outlook
> wouldn't run.

That should not be necessary - how did you migrate the old profiles? If you
didn't migrate/copy the old ones, you had to create new ones (you have a new
domain with the same name, but the SIDs won't match)
>
> When copying the User folders, I made each user the owner of their
> own user folders. I also changed ownership for the local user folder
> (Docs and settings)
> on each PC, but still no go; unless the domain user is a local
> administrator they
> can't use their settings as it is not saved (no write rights).
> I wonder if this is any connection to the DNS problem (permissions
> somewhere)?

Doubtful.
>
> Now, this is strange to me: if on a particular PC, the computer
> account is not
> created via changing domain membership, the user of the PC can login
> to the new server. On the server, event log says the PC tried to
> join but was rejected
> but of mismatched SID yet the user is able to logon. Furthermore, the
> user's
> profile and settings have no issue even with restricted rights unlike
> above.
>
> Any idea why, or an alternative workaround appreciated.

Again, more info of how you migrated the profiles might help. If you log in
once as the new domain user, then log in as domain admin, you might be able
to copy the old profile in control panel | system (user profiles settings) -
but this can be a PITA. Depending on the number of users it may be just
easier to manually recreate them. Don't expect the old roaming profile
folders to work 'out of the box'. Make sure you always redirect My Documents
to the users' home directories, don't let users store files on their
desktops - and profiles are a lot easier to manage. I'm presuming the old
profile folders are there and the users now have ownership to them - so you
can copy out what you need.
>
> TIA,
> Eugene Tan

Relevant Pages

  • RE: Migrate from untrusted hardware (install does have damage)
    ... This rule can be applied to ALL Windows OS not only SBS. ... When we use SBS 2003 server backup, ... Use Outlook to export the contents in the public folders to .pst files ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)
  • RE: Restoring SBS2003 on a new Server
    ... This rule can be applied to ALL Windows OS not only SBS. ... When we use SBS 2003 server backup, ... Use Outlook to export the contents in the public folders to .pst files ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)
  • RE: Subject: RE: Exported files with Exmerge seem too small
    ... Since you reinstall SBS Server 2003 with a clean install, ... you can clean install the SBS 2003 server with a new ... Another way is to create a local profile, ... Click Personal Folders File, ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS2003 Migration problem
    ... When we use SBS 2003 server ... Use Outlook to export the contents in the public folders to .pst files ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 - Move Profiles, Etc. from 2000 Server
    ... moving PST on old server. ... guide in SBS 2003, we have a white paper for this kinds of migration, ... Another way is to create a local profile, ... Click Personal Folders File, ...
    (microsoft.public.windows.server.sbs)
Loading