Re: Urgent! New router and big disaster

okay, i have this..

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
"Merv Porter [SBS-MVP]" wrote:

Focus, Kimmy, Focus. Let's get your network working properly before we talk
about optimum (or other) configurations.

--
Merv Porter [SBS MVP]
===================================
"Kimmy" <Kimmy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F05B1D6C-A6A4-4476-B188-0FFB8094C99E@xxxxxxxxxxxxxxxx
I just doubled check with my ISP provider, and I can get another static ip
on
my account to run the extra board rooms/ conference rooms and offices. So
with that in mind, my internet connection is a direct line from a wireless
dish that I have currently plugged into the router. I have 1- D-link
router,
1- Dlink 8 port gigabit switch 1 -D-link 24 port switch, and a server with
two nics. If there is a better setup, than what I am trying to do I'm all
ears.

"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
.

Relevant Pages

  • Re: In-Place Upgrade From Windows 2K Server
    ... Is the DHCP server authorized in Active directory and the scope activated? ... I have tried to disable the DHCP on the router and set up a scope on ... DHCP and DNS is done from the DC without any problem and you ... for the physical connection, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cannot connect to RWW from home PC
    ... eth0 172.26.0.1/16 Extra none ... That would be the address you need a DNS record for. ... One question - if I reset the Thomson Router will that clear all the ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... No 10.0.0.138 is the address used to log onto Thomson's router to make the ... On the DNS question I can add an MX record in the DNS area of GoDaddy's ... eth0 172.26.0.1/16 Extra none ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Server 2000 + file sharing + connection issues
    ... > connection via Windows 2000 Server. ... > return DNS errors or "Action Cancelled"). ... > Netgear ADSL Firewall Router DG384G ...
    (microsoft.public.win2000.networking)
  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)