Re: Win2000 SBS moved to new location... logon issue

Glad you got it fixed!

--
Merv Porter [SBS-MVP]
============================

"euvloon" <euvloon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D740FDD1-AEA7-49AC-9578-4684DE7C5E57@xxxxxxxxxxxxxxxx
Problem solved... thank you for all your help.
There were two problems...
1. I'm a NT guy not Win2k so I had the network configured wrong for DNS
(AD)
2. A chunk of spyware was in the server which caused all the shares to
vanish.

The DNS error never caused a problem on my old network... I'm assumimg
that
was because my old NT network was migrated to win2k which left enough of
the
old stuff in place to make up for the incorrect DNS configuration on the
new
(at the time) Win2K server. It worked for years that way without a
problem
but when I moved the entire network to a new location, all hell broke
loose.
Basically, my DNS on the W2k server was configured like NT with WINS. The
client computers were all pointing to the ISP DNS instead of the W2K DNS.
Also, the W2K DNS was pointing to the ISP DNS instead of itself. Once I
corrected the DNS configuration errors I re-ran the ICW and that fixed
90%
of the problems. I also found a few services that weren't running and
when I
started them that fixed the rest of the problems.

The spyware was interfering with required system shares... removing the
spyware removed that problem.

Thanks again for your help.

"Merv Porter [SBS-MVP]" wrote:

Also, please post an ipconfig /all for the SBS server.

--
Merv Porter [SBS-MVP]
============================

"euvloon" <euvloon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FF9556C3-1427-41DC-93B5-AF830F112868@xxxxxxxxxxxxxxxx
I'll try to copy the log file it created.

"euvloon" wrote:

ICW gets an error when trying to configure the exchange server...
something
about a network not found.

"euvloon" wrote:

I should have mentioned... I'm typing this reply right now through
the
VPN
connection to the Watchguard. Users that don't have a problem
loging
on
locally also don't have a problem with the VPN access. I'm certain
it's the
user not the computer because both my wife and myself have logon
accounts
with the server and I can logon throught the VPN with my account but
not with
hers using the same computer.

"euvloon" wrote:

I have a Watchguard FireBox X500 that handles VPN. The VPN users
are
having
a mixed bag of problems ranging from no problem to can't logon at
all. I'm
hoping your prior suggestions will fix the VPN issues as well.

"Merv Porter [SBS-MVP]" wrote:

For Remote access (VPN), you *may* also have to re-run the ISA
VPN
Wizard:

Start | Programs | Microsoft ISA Server | ISA Management |
Internet
Security
and Acceleration Server | Servers and Arrays |
<yourSBSServername>
| (rt.
click) Network Configurations | Allow VPN Client Connections

--
Merv Porter [SBS-MVP]
============================

"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in
message
news:eWzhp9H6GHA.2120@xxxxxxxxxxxxxxxxxxxxxxx
Since you made changes to a NIC, you need to re-run ICW so
that
SBS can
properly incorporate the changes.

ICW should display all your original settings. Run through
the
screens
and document everything (Alt-Print Screen and paste the
screens
into a
Word document is a good way to do this). When you get to the
last screen,
click Cancel.

Then re-run ICW and input the new info for the NIC changes you
made. This
will occur in the first few screens of ICW. The email
settings,
Internet
Domain Name and POIP3 settings (if you use POP3 Connector)
should
not
change. When you get to ISA, click on "Enable ISA Packet
Filtering". ICW
will display your original ISA settings so you don't need to
change
anything on this screen. After you click Next, a message will
pop up
saying that existing ISA filters will be disabled. Click OK
and
then
finish ICW.

The popup message you got about ISA filters means that any
"custom" ISA
filters that you have created will be disabled. If you
haven't
created
any "custom" filters, you're all set. If you have created
custom
filters
since the original setup, after ICW is done go into the ISA
Management
console and simply turn them back on (click the checkbox to
"Enable"
them). This would be done at:

Start | Programs | Microsoft ISA Server | ISA Management |
Internet
Security and Acceleration Server | Servers and Arrays |
<yourSBSServername> | Access Policy | IP Packet Filters.
Then
in the
right pane, click on any disabled custom filters that you want
to
use and
check the "Enable this Filter" box.

--
Merv Porter [SBS-MVP]
============================

"euvloon" <euvloon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1B27F3F3-2BB6-43D8-8F92-EE523AA83322@xxxxxxxxxxxxxxxx
No I didn't. I started to do that after I noticed all the
seemingly
unrelated problems but I stopped myself because I wasn't sure
that it
would
fix the problem or make matters worse. The wizard asks
numerous
questions
about Internet Access and Exchange settings (SMTP, POP3 etc.)
and
provides
for "Leave the Settings as is"... I wasn't 100% certain of
the
correct
response so I backed out.

"Merv Porter [SBS-MVP]" wrote:

Did you re-run ICW (Internet Connection Wizard) after
changing
the
external
NIC IP address?

--
Merv Porter [SBS-MVP]
============================

"euvloon" <euvloon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:EA1D6E55-6C49-42EE-8D55-1D6213A00BEC@xxxxxxxxxxxxxxxx
I recently moved a Windows 2000 SBS and network to a new
location. All
equipment including computers, switches, firewall,
printers... every
piece
of
equipmtent in the entire network was reassembled exactly
as
it was in
the
old
building. The Compaq Proliant server which hosts the
Windows
2000 SBS
is
a
multi-homed system... the only configuration I changed was
the IP
address
of
the external NIC (I also changed the trusted interface on
the
Watchguard
but
that is not relevant to my current problem)... Once I had
the network
back
up and running I noticed that all the XP clients could
join
the Domain
(same
domain name, I didn't change anything) but none of the
Win98
clients
could
join. I also noticed that certain services... although
running...
don't
appear to function, like Routing and Remote Access. If I
call up the
RRA
manager my "server name" is X'd out. Also, although email
is
working
(Exchange 2000) odd error messages are written to the
event
logs about
failed
authorizations and Global promotion. Also, error messages
about
broken
trusts and invalid SID id's are written to the event logs
along with
messages
about "can't find network name". There are so many things
wrong that
I
find
it difficult to even categorize the problems however, the
server is
running
and performing reasonably well (except for the Win98
clients
who can't
logon
at all). Internet access is fine... email works fine (if
you
ignore
the
errors in the event logs)... file sharing and printing are
all working
fine.
I'm guessing that the problems must originate from the
external NIC IP
change but I'm at a loss to explain how. I did a scan of
the
registry
for
the old external NIC IP just to see if any referrences
still
existed
but
there were none.
I'm running SP4 of Windows 2000 server, so there are no
additional
SP's to
be applied. Any ideas??? I'm stumped.













.

Relevant Pages

  • Random Network Disconnects
    ... network and the only way I can seem to get it back up is to restart the box. ... Testing IpConfig - pinging the Secondary WINS server... ... DNS Host Name: itdspstest01.itd.edited.edited ... Provider Version:2 ...
    (microsoft.public.windows.server.dns)
  • RE: Server 2003 Network problems since IP address change
    ... Rightclick "My Computer", properties, Computer name or network identification, ... Is there any firewall running on client or server? ... Is the Primary DNS ... of zone WSW.local. ...
    (microsoft.public.windows.server.networking)
  • Re: About DNS naming convention for Active Directory
    ... Here's what I did so far, I set up a private network consists of the ... I did an in-place upgrade of the NT4 PDC to Active Directory 2003, ... I had no DNS service at all. ... Joined the 2003 Server as a member server and that went well too. ...
    (microsoft.public.windows.server.dns)
  • Re: Single NIC configuration with cable modem/router
    ... Internal or single network adapter configuration ... Verify the Domain Name System (DNS) pointers. ... Right-click Server Local Area Connection, ...
    (microsoft.public.windows.server.sbs)
  • RE: Strange Irregular DNS/Networking Problems
    ... My network is not a complicated set up and only has one domain controller. ... problems with DNS resolving after changing DNS servers. ... I was already using the server for DHCP. ...
    (microsoft.public.windows.server.dns)
Loading