Re: Urgent! New router and big disaster

Also, it might be a good time to go to the router's configuration page, and
see what it has to say. Is it connected, and what dns servers is it pointing
to? Perhaps they're pooched. If you could easily connect a machine on one of
the router ports (and get the nic configured correctly) you might be able to
determine if there's a working internet connection, or not.

This thread shows how hard it can be to get anything done in a newsgroup
setting. An experienced SBS technician would have this sorted in less than
10 minutes if he was at your premises ;-/.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23HGGR8YQGHA.3896@xxxxxxxxxxxxxxxxxxxxxxx
Go back to pointing the external NIC DNS Servers to the SBS server IP
address (192.168.16.2).

After that, make sure the DHCP Client Service is running on the server.

No DNS Name Resolution If DHCP Client Service Is Not Running
http://support.microsoft.com/kb/q268674/

--
Merv Porter [SBS MVP]
===================================
"Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
wrote in message news:%23XzuE4YQGHA.2300@xxxxxxxxxxxxxxxxxxxxxxx
Whooops, local router device is the wrong answer ;-).

You have a full-time broadband connection.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Kimmy" <Kimmy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:97BAB5D4-7850-40B0-BEA2-E9B58F95F90A@xxxxxxxxxxxxxxxx
Okay, when I run the CEICW this is what I see...
First Page of the Internet Connection Wizard, I select my Broadband
connection.
Next I Select a local router device with an ip address. The next page
are
the DNS Server addresses provided by my ISP, and the local IP address of
router,which are already in.

The Next Page is the network connection page, Under ISP network I have
the
Network connection, but I can't change the ip address or the subnet
mask,
same as the Server Local Area Connection, I can't change addresses there
either.

After that I get the rest, firewall, web server certificate, internet
email
and so on. I am not sure how I can
use the CEICW to make the changes you have listed. Or have I
misunderstood.

"CO-DBA-SC-EL" wrote:

You're getting close. Since you can reach an external web site by using
its
IP it means that your problem is now DNS. I don't see how your settings
could work. In the TCP/IP properties for the external NIC, you need to
specify an external DNS server for DNS, instead of the server's own IP
address. You should do that in the CEICW, that way it will set up the
DNS
forwarding to work correctly. When the CEICW asks you for the
configuration
for the external NIC, use:
IP Address 192.168.0.99 (See Note 1)
Subnet Mask : 255.255.255.0
Default Gateway: 192.168.0.1
DNS Servers: 192.168.0.1 (See Note 2)

Note 1. 192.168.0.100 looks like an address in the DHCP range of the
router.
You should give your SBS a fixed external address so you can forward
ports
to it reliably in the router. I don't have the D-Link doc but x.x.x.99
should be outside its DHCP range. If not pick another one. Why do that
if
the SBS is the only computer connected to the router? Because some day
you
might try to debug something else, plug a computer in the router while
the
SBS is off or disconnected, then plug the SBS back in and discover that
the
other computer has now been given the address you thought was the SBS's
own.
Then of course RWW and all those goodies quit working. Play it safe.
Use a
fixed address outside the DHCP range of the router.
Note 2. Normally the router will forward DNS requests. You may be able
to
speed things up by specifying the IP address of your ISP's DNS servers
instead of the router -- the router will just pass that through instead
of
actively forwarding.

C_O

"Kimmy" <Kimmy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C56EA7C3-EAE0-4D4F-9BBB-DFA8FBB9DC11@xxxxxxxxxxxxxxxx
I checked the binding order and the Server Local area connection is at
the
top.

I should have been more clear about internet connection..
- when we open internet explorer the company web is shown, when we
type in
an address... http:www.google.ca, we get page cannot be displayed.
But if
I
type the ip address 65.98.45.220 the webpage loads. (this is true for
Both
the SBS and client stations)
I just read somewhere in another posting about nslookup.exe, and
thought I
would give it a try. I got this..
***Can't find server name for address 192.168.16.2: Non-existent
domain
Default Server: Unknown
Address: 192.168.16.2
( I found that in the DNS - clicked my server name and ran the lookup
tool)

"Merv Porter [SBS-MVP]" wrote:


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.

Check Binding order
------------------------
Right click My Network Places...Properties. Highlight the Internal
NIC.
Then
select Advanced...Advanced Settings from the top menu for that
window.
This
will check the bindings.

The Internal NIC should be displayed first followed by the External
NIC.
If
not, move the Internal NIC to the top of the list.
The Internal NIC should have File and Printer Sharing bound
(checkmarked)
to
the TCP/IP Protocol.
The Internal NIC should have Client for Microsoft Networks bound
(checkmarked) to the TCP/IP Protocol.
------------------------

Is the Internal NIC at the top of the list?

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.

What is 65.98.45.220? If neother SBS server nor client workstation
had
Internet access, how could they view anything at this public
(Internet)
IP
address?

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

"Kimmy" <Kimmy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:41894A1D-D2B3-49C0-AB14-AD2D5EA865E8@xxxxxxxxxxxxxxxx
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






.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... by CEICW for any type of connection other than full time broadband was ... exists - is completely transparent to the SBS. ... "local router with an IP address" is the setup that matches her network. ... between the server and my cable modem. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... connected to is; what type of connection; or even whether a connection ... exists - is completely transparent to the SBS. ... "local router with an IP address" is the setup that matches her network. ... between the server and my cable modem. ...
    (microsoft.public.windows.server.sbs)
  • Re: Internet access problem caused by DNS failure
    ... I would do a test to find out if it is the router or you SBS that is causing ... Change the DNS ... I can vpn in to the router from outside. ... Ethernet adapter Wireless Network Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... seleting full time broadband connection. ... Les Connor [SBS Community Member - SBS MVP] ... check the router as well and unless I missed a firewall setting on it, ... Anyway the Server Ipconfig /all is this... ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... DNS on your server is broken. ... Les Connor [SBS Community Member - SBS MVP] ... and put in the ip of the router. ... The local router has the broadband connection ...
    (microsoft.public.windows.server.sbs)