Re: Network Gone Kaput
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Thu, 12 Apr 2007 08:15:58 +1000
the .org is _probably_ coming from the router's DHCP.
As Les says, the network is misconfigured.
"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message
news:5175864F-00BF-4A3D-A10E-47EEA08CF4A6@xxxxxxxxxxxxxxxx
You're jumping into the fire.
Your network isn't configured correctly, and with these changes it's
further off where it needs to be. You should seriously consider disabling
DHCP on your router, and enabling it on your SBS. You also need to get the
public DNS IP references off the lan, and run the CEICW to either
configure root hints or your ISP's DNS server IPs as forwarders.
The following document should help you.
825763 How to configure Internet access in Windows Small Business Server
2003
http://support.microsoft.com/?id=825763
Your workstation(s) also may not be correctly joined to the domain, I saw
in your previous post the .local domain on the server, but a .org domain
on the workstation.
--
Les Connor [SBS MVP]
"Acupro Tech" <AcuproTech@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6710BEB8-A951-4DF1-B500-8C882053D262@xxxxxxxxxxxxxxxx
Ok problem solved. Here is what I did can you explain why it worked?
1) Uninstalled SP2 for 2003 (which was installed Monday as it turns out)
which caused no change.
2) Uninstalled automatic update from Sunday at 3:00AM which caused no
change.
3) Disabled IP routing and Remote Access and restarted Windows Firewall.
Problem resolved.
What triggered me to do the last step you ask?
The server started getting an error message at boot that on or more
services
failed to start at the same time the connection issue began. Logical
assumption was that whatever triggered that also triggered this problem.
I
searched the event viewer and discovered it was Windows Firewall and ICS
Service that was failing and it pointed to IP ROuting and Remote Access
Service running as the probable cuplrit. So I disabled IP Routing and
Enabled WF and ICS Service and it started fine and then all server
resources
were once again available.
"Les Connor [SBS MVP]" wrote:
Something is fishy.
The server didn't auto-update at 3:00 am, by chance?
Is Windows Server SP2 installed, if so when, and has the network worked
since that time?
With a single nic SBS, the workstations don't go "through" the SBS.
What make and model of NIC is the SBS using?
Please post there result of 'ipconfig /all' run from a command prompt at
the
server, and also one from a workstation.
--
Les Connor [SBS MVP]
"Acupro Tech" <AcuproTech@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:202ED8EE-A3E5-464F-9C07-3131A30E4524@xxxxxxxxxxxxxxxx
Have a network that working fine until Sunday 3AM and then it fell on
its
lips.
Configuration:
1 SBS2003 Server SP2, Single NIC ran to a Netgear 8-Port VPN Firewall
Router
Wire run to Rackmount HUB from Netgear Router
7 computers currently configured to run through SBS for email, shared
drives
and internet.
All computers can ping all computers and netgear router except that
the
seven cannot ping the server.
Specifically:
1) The server can ping the clients and the router
2) The clients can ping the router and each other
3) The clients CANNOT ping the server
Originally none of the server resources were available.
If I change the gateway on the clients from the servers ip address to
the
routers ip address all the computers are able to access the internet.
Of
course they are still unable to use email and access data on the
server.
--
Chris
.
- References:
- Re: Network Gone Kaput
- From: Les Connor [SBS MVP]
- Re: Network Gone Kaput
- From: Acupro Tech
- Re: Network Gone Kaput
- From: Les Connor [SBS MVP]
- Re: Network Gone Kaput
- Prev by Date: Re: POP3 Schedule
- Next by Date: Re: How do you set your IMF?
- Previous by thread: Re: Network Gone Kaput
- Next by thread: The local policy of this system does not permit you to logon interactively
- Index(es):
Relevant Pages
|
