Re: Urgent! New router and big disaster
- From: Kimmy <Kimmy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 6 Mar 2006 16:19:27 -0800
Been having a a lot of trouble. The orignial router died and now we are
using a D-Link 604. My problem is this:
1 -I have the set up done just like this...
http://www.smallbizserver.net/Default.aspx?tabid=266&articleType=ArticleView&articleId=76
However, when I checked the binding on the external nic there was no TCP/IP
in the list, just File and Printer Sharing and the Microsoft Client Networks
were the only two in the list and neither of them are checked off. After
running the internet connection wizard, no internet was available for either
the SBS or the Client by using the test page www.dnslookup.com, but each can
view 65.98.45.220.
The Current ipconfig/all from server is this
Server Local Area Connection:
Connection-specific DNS Suffix:
Description: Intel Pro/1000
Physical Address: 00-14-22-B4_12-CE
DHCP Enabled : NO
IP Address 192.168.16.2
Subnet Mask : 255.255.255.0
Default Gateway:
DNS Servers: 192.168.16.2
Primary Wins Server 192.168.16.2
Ethernet Network Connection
Connection-specific DNS Suffix:
Description: BroadCom NetXtream
Physical Address: 00-10-18-18-31-C2
DHCP Enabled : NO
IP Address 192.168.0.100
Subnet Mask : 255.255.255.0
Default Gateway: 192.168.0.1
DNS Servers: 192.168.16.2
NetBios Over TCPIP: Diabled
Any ideas?
Other info... Before I ran the internet connection wizard, I also disabled
the UPNP on the router itself. I have checked the DNS Service and it is
running, also is the DCHP Service.
I wonder if I may have missed a firewall setting on the router as well.
"CO-DBA-SC-EL" wrote:
Hmmm. In a 2-NIC setup changing the router (which feeds the WAN side of the.
SBS) should have nothing to do with the inability of the clients to login to
the domain. Completely separate networks. The IPconfig for the client shows
that the client is not able to get an address from the DHCP server on the
SBS.
Now, a problem could occur if the physical net was configured to use the
router's LAN switch to connect the workstations (both SBS NICs into the same
switch) which in theory should work but is of course a very bad practice. If
that is the problem, try to fix that, using the diagram in the SBS
documentation (such as it is...). Assuming that this is not the problem...
First check whether the DHCP service is running. If it is not, start it,
then try to figure out why it did not start in the first place.
If that does not fix the problem, go through the following steps:
1. Verify that the workstations can physically connect to the LAN side of
the SBS. Since it looks like the workstations are set up to use DHCP, a
quick and dirty way to do that would be (a) disconnect everything from the
router then (b) to move the cable from the LAN side NIC of the SBS to a LAN
port on the router then (c) turn on the router, give it time to boot and do
an ipconfig -reset on a workstation then check whether it got an IP address
from the router and that it can ping the router. If that doesn't work, first
do a deep reset of the router and try again. If after that it still does not
work, look for a bad cable or bad switch in the LAN or some other LAN config
problem.
2. Assuming that step 1 is fixed, take this opportunity to log into the
router and verity that it is set up correctly. It should have DHCP turned on
and have its WAN side configured properly, including the ISP DNS and gateway
addresses if the WAN side of the router is not using DHCP. Don't bother with
port forwarding yet. Making sure that the firewall on the workstation is
enabled (or using a test laptop instead of the workstation), connect the WAN
side of the router and check that the workstation can connect to the
Internet. If that works, then the router should not be a problem and you can
focus on the SBS. If that doesn't work, pretend that the router is working
for the purpose of step 3, but you will need a router...
3. With all physical connections correct (as in the SBS documentation
diagram for 2-NIC setup with a router), run the CEICW. Use the vanilla
settings. While you are at it, set up a LAN side address of 192.168.x.2 for
your SBS, where x is anything excep 0, 1, 2 or 13. This will allow you to
substitute any router (at least from the brands I've tried) without having
to worry about subnet conflict between the WAN and LAN side. When it comes
to router UPNP say that your router is not UPNP, and look up the "More Info"
that tells you which ports you will need to forward on the router. Port
forwarding on your perimeter device is something you probably want to be
able to control yourself. Also, if you control port forwarding on the router
yourself, you can replace the router at will without ever needing to change
anything in the SBS configuration.
4. Check the Services to verify that the DHCP service is running. Go to a
workstation and verify that it can get an IP address through DHCP and that
you can ping the SBS--it should show up as the gateway and DNS server in the
IPconfig for the workstation. If this doesn't work, then you have a more
serious problem with your SBS. Call for help.
5. If steps 1 to 4 succeeded, then try to king a known good test address
(e.g. www.dnsreports.com) on the Internet from a workstation. If that
doesn't work (not found), try to ping a known IP address (e.g.
65.98.45.220). If that works but pinging by name did not work, you have a
DNS problem. Check that the DNS configuration in the CEICW is correct. If
you had made manual modifications to the SBS DNS settings, go back to your
setup nodes and try to undo them before running the CEICW. If that still
doesn't work, call for help.
Let us know how you've done. Sleeplessness induces people to make strange
errors... so be careful.
C_O
..
"Jan" <jan@.n.o.com> wrote in message
news:Ob1SWtCQGHA.1040@xxxxxxxxxxxxxxxxxxxxxxx
It looks like new router configuration was different from one that died.
Post output of "ipconfig /all" from server and one workstation connected
to 24 port switch.
Should be able to give you simple instructions to get back to where you
where before this incident.
--
Jan Wakulicz
www.micropol.com.au
"Kimmy" <Kimmy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C85BE8C6-2E8A-4DC6-AB7A-11CD42D0716B@xxxxxxxxxxxxxxxx
quick brief on orginal setup
Dell Power 1800 server running SBS2003 standard with 2 nics
1 D-link 8 port router & 1- 24 port switch
D-link connected to ISP with a stactic ip and server- onbard nic
connected
to switch.
Orginal install went off with out a hitch including all updates ect. For
a
week clients could communicate with server.
Yesterday the router dies, and I quickly swapted it with another D-link
router this one smaller -only a four port. When the router died, other
than
no internet access, the client machines could still connect to server.
After I swaped the router everything was still fine.
This morning, I had to go clean up my network room and wires. During this
I
shut down the server, and removed of from the room. It was down for about
5
hours.
Then I set it back up, all the same- i didn't touch a setting, and now my
clients can't login. The administrator can log in client machines,
release/renew the ip address, look at network places, see the server but
cant
connect. No internet access either.
Okay so back at the server -no internet connection but can see the
internal
website. The external nic is set to auto get ip from router, but the
primary
dns is the ip address of the local nic. When I change that to the ip of
the
router I can get internet on the server. Ran the CEICW... doh! The wizard
poped up with that the router is a plug in play and it wanted to
configure
it. Now everything is so totally messed.
I cant get any clients to log in but when i set the ip on the external
nic
back to the router ip, I can reach the remote server login page on my
laptop.
I have ran the change server ip wizard, but nothing.
Please I need to have this whole thing back up and running by Mon.
morning,
so please give very deatiled instructions if ya got them. I have been
going
on less than 3 hours sleep, and if you can come up with a less than
perfect
quick fix until next weekend, I am all ears.
Thanks
- Follow-Ups:
- Re: Urgent! New router and big disaster
- From: Merv Porter [SBS-MVP]
- Re: Urgent! New router and big disaster
- References:
- Re: Urgent! New router and big disaster
- From: Jan
- Re: Urgent! New router and big disaster
- From: CO-DBA-SC-EL
- Re: Urgent! New router and big disaster
- Prev by Date: Re: SBS server blue blank screen - but running.... need to reboot
- Next by Date: Re: RWW Issues
- Previous by thread: Re: Urgent! New router and big disaster
- Next by thread: Re: Urgent! New router and big disaster
- Index(es):
Relevant Pages
|
