Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
- From: "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com>
- Date: Fri, 14 Sep 2007 11:23:37 -0400
Hi:
At least we know what the probable error is.
I would ask in the W2K3 group, (not SBS :-) ), and not mention SBS at least
in the first post.
Larry
"Bob Randall" <BobRandall@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5CB5B570-0F58-4304-A2C0-1E3646EA812E@xxxxxxxxxxxxxxxx
OK, here is something - this is from the DCDiag text file:
-----------------------
The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain
special-tees.com:
The error was: "This operation returned because the timeout period
expired."
(error code 0x000005B4 ERROR_TIMEOUT)
The query was for the SRV record for _ldap._tcp.dc._msdcs.special-tees.com
The DNS servers used by this computer for name resolution are not
responding. This computer is configured to use DNS servers with the
following
IP addresses:
192.168.1.1
Verify that this computer is connected to the network, that these are the
correct DNS server IP addresses, and that at least one of the DNS servers
is
running.
--------------------------------------------
There is the problem ... how do I fix it??? Do I add a SRTV record for
special-tees.com pointing to the internet, or a bogus entry since there is
no
longer that Domain with that address?
Bob
"Larry Struckmeyer" wrote:
Sorry, I missed the non sbs part.
So lets see:
What happens if you just turn the SBS 2000 off or remove it from the
wires.
Errors in your event logs on the workstations or W2k3 server?
Errors in netdiag or dcdiag on the server? (you may need to load support
tools from your W2K3 cd.
Proxy setting still in IE tools, connections, lan settings?
if you want, post back the output from ipconfig /all > filename.txt for
server and workstation.
Larry
"Bob Randall" <BobRandall@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:08A7C941-28C0-4B5E-90CB-36A3170EC529@xxxxxxxxxxxxxxxx
The server I am migrating away from is SBS 2000 and I am migrating to
Windows
2003 Server R2, not SBS 2003, that is why I posted here in this
newsgroup.
Since I moved to a straight 2003 domain, I just manually added all of
the
workstations to the new Domain, which worked fine. I realize that I may
have
caused a problem by continuing with the .com suffix, but I don't think
that
is what is causing my problem right now. It may be DNS, but there are
no
entries in the new Server 2003 DNS that look suspect. I can't figure
out
how
the workstations still know anything about the old SBS 2000 ISA server.
I
removed the DC and DNS roles from that server, but it still does have
ISA
2000 on it. The are all on new IP addresses too, so how are the
10.0.0.0
workstations finding the old 192.168.0.1 gateway? Nothing in their
configuration tells them to go that way, and I removed the old ISA
Firewall
client from all of the workstations before I migrated them to the new
Domain.
Bob
"Larry Struckmeyer" wrote:
Hi Bob:
This is the SBS 2000 group. You might get more help in the SBS 2003
group.
microsoft.public.windows.server.sbs
For starters, it is usually not recommended that the SBS internal
domain
name end in .com or .net or any of the public suffixes. Better that
it
use
..LAN or .local or .office.
Secondly, did you use the wizards to create the users and computes,
and
did
you join the workstations using https://servername/connectcomputer?
Most connectivity problems are caused by DNS problems.
I would repost this into the sbs 2003 group, along with a cut and past
of
ipconfig /all > c:\filename.txt from both the server and a
workstation.
No
need to change anything.
Also, 1 nic or 2?
Larry
"Bob Randall" <BobRandall@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1C6ABD90-4DBD-47BB-90FE-897FF4580090@xxxxxxxxxxxxxxxx
I have a strange issue that I need help with - here are the details:
I recently moved a small business office off of Small Business
Server
2000
which was running as a DC, DNS Server, DHCP, and IS 2000. This
office
has
10
users, so I went the fully manual way. I took a new Windows 2003 R2
server,
built a new DC, and added DNS and DHCP services to it. I changed the
Domain
name when I did it as well, because the person who created the
initial
SBS
2000 domain named it the
same as their registered domain name (which caused issues with the
externally hosted web site,etc). The SBS 2000 domain name was
special-tees.com, and I built the new domain as
home.special-tees.com.
I
also switched the IP addressing scheme from a 192.168.0.0 group on
SBS
2000
to a 10.0.0.0 group on the new domain.
While both domains were running at the same time I went to each
workstation,
removed them from the SBS 2000 domain, removed the ISA 2000 Firewall
client,
removed them from the old domain and put them in a Workgroup,
rebooted,
joined the new domain, renewed their IP addresses with DHCP on the
new
Windows 2003 R2 server (10.0.0.0), and configured the workstations
Apps,
etc
... I kept both domains running at the same time because I wanted to
make
sure I properly removed each workstation for the old domain so no
traces
of
the old domain would be left behind. Since they are completely
different
IP
ranges, they were never using the same default gateway address. I
did
that
for all of the workstations and they are all communicating fine with
one
another. I then demoted the old SBS 2000
server and removed the AD, DNS, and DHCP roles that it had.
Here is the issue - they are having intermittent internet
connectivity
issues. If I unplug the two Ethernet cables from the ISA 2000 server
(which
was acting as their Internet proxy before we migrated to the new
Domain),
they have an intermittent internet connection. Sometimes it is
really
slow,
sometimes it if fine, sometimes they have no connection at all. If
there
is
no connection I can go to the ISA server, plug the cables back in,
and
the
Internet connection is back right away at full speed. If I leave it
plugged
in, the same thing happens - the internet access degrades and
becomes
intermittent. If I unplug them the internet connection comes back
immediately
- then the same thing happens again. What is going on? There are two
different IP addressing schemes, none of the systems are pointing to
the
old
gateway AT ALL on the ISA 2000 server, but for some reason the
clients
are
occasionally trying to get to the internet via the old ISA server!
Am I
missing something here? I even cleared the DNS cache from the
workstations
and nothing .
Anyone have any ideas??
Bob
.
- References:
- Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
- From: Larry Struckmeyer
- Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
- From: Bob Randall
- Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
- From: Larry Struckmeyer
- Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
- From: Bob Randall
- Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
- Prev by Date: Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
- Next by Date: Re: ISA 2000 with High Speed ADSL
- Previous by thread: Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
- Next by thread: Re: Strange Issue Moving from SBS 2000 to Server 2003 R2
- Index(es):
Relevant Pages
|
