Configuring DNS/WINS on SBS 2003 with ATT provider
Webtechie
I work for a company that wanted to created a network and network
application. We bought SBS 2003. I've installed it and SQl Server. I've
written the application and everything works good. The client server app
works well. All clients are able to insert and receive data from the SQL
Server.
But I am confused as to how to configure DNS and/or WINS. It is a very
small network less then 20 pcs and one printer. The server is configured to
get DHCP and DNS dynamically. We have an HP Switch which has a static IP
address. We have a router on that. I guess the phones and all going through
the switch. All of the pcs are going through the router. I'm not sure why
the other guy set it up as this, but he is gone.
The clients are set up to also get the dns and dhcp dynamically. But
logging on takes forever. I'm thinking I need to set up DNS or Wins. In my
last job, I set up DNS with a static IP address and then configured the
clients to look to that server as the DNS server.
How do you configure a network with a ISP handling dhcp and dns? Is that
the proper setup?
Thanks
Tony
Ace Fekay [MCT]
news:19CF8973-B53B-47C2...@microsoft.com...
If you are seeing "long logon times," it is indicative of misconfigured DNS
settings. Please post an unedited ipconfig /all of the SBS and of a sample
workstation.
Also, is the DHCP server the SBS or the router?
Did you ever run the wizard to setup the SBS?
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Webtechie
Ok, here goes.
Server Config
=========
Windows IP Configuration
Host Name . . . . . . . . . . . . : cbssrvr01
Primary Dns Suffix . . . . . . . : CBS.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : CBS.local
Belkin
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Realtek RTL8168/8111/8112 PCI-E
Gigabit Ethernet NIC
Physical Address. . . . . . . . . : 00-24-8C-E6-73-9E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.19
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Primary WINS Server . . . . . . . : 70.247.109.1
Lease Obtained. . . . . . . . . . : Monday, December 14, 2009 6:57:26 PM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038 9:14:07 PM
Ethernet adapter Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 802.11n Wireless LAN Card
Physical Address. . . . . . . . . : 00-22-43-64-82-21
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 70.247.109.31
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 70.247.109.1
DNS Servers . . . . . . . . . . . : 4.1.1.1
4.2.2.2
NetBIOS over Tcpip. . . . . . . . : Disabled
Client
====
Windows IP Configuration
Host Name . . . . . . . . . . . . : CBFPC09
Primary Dns Suffix . . . . . . . : CBS.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : CBS.local
Belkin
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Realtek RTL8168/8111 PCI-E
Gigabit Ethernet NIC
Physical Address. . . . . . . . . : 00-24-8C-89-95-6D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.22
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Tuesday, December 15, 2009
11:27:52 AM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038 9:14:07
PM
"Ace Fekay [MCT]" wrote:
> .
>
Ace Fekay [MCT]
Hi Webtechie,
Thanks for posting this info.
I see some inconsistencies that do not make sense. The SBS internal
interface is 192.168.2.19. Then what is 192.168.2.1? That IP is used on the
client machine for DNS, DHCP and the gateway. Please elaborate.
Thank you,
Ace
kj [SBS MVP]
Pretty sure it's his Belkin 'router' and it's configured out of the box.
(Needs to have DHCP disabled on it and restart the SBS's.)
--
/kj
Duncan McC
You must use SBS to do DHCP. Don't worry about internet connectivity,
you do that through SBS as well, by setting forwarders in DNS (so that
SBS does the DNS, and hands out unknown routes to the forwarded
addresses (your ISP's DNS).
Just run the CEICW wizard to configure it all - it'll do the lot for you
in a minute. (Turn OFF any DHCP first in your router).
--
Duncan.
In article <19CF8973-B53B-47C2...@microsoft.com>,
Webt...@discussions.microsoft.com says...
Webtechie
The server CBSSRVR01 has an internal ip address of 192.168.2.19.
I just tried to ipconfig /release and ipconfig /renew at the server.
It tells me that 192.168.2.1 is the default gateway. I checked the tcp/ip
properties and everything is set to obtain dynamically. I went into advanced
and there is nothing being set.
I'm not sure what is telling the serving its default gateway is 192.168.2.1.
Tony
"Ace Fekay [MCT]" wrote:
> .
>
Ace Fekay [MCT]
> Thank you so much for trying to help. I REALLY appreciate it.
>
> The server CBSSRVR01 has an internal ip address of 192.168.2.19.
> I just tried to ipconfig /release and ipconfig /renew at the server.
>
> It tells me that 192.168.2.1 is the default gateway. I checked the tcp/ip
> properties and everything is set to obtain dynamically. I went into
> advanced
> and there is nothing being set.
>
> I'm not sure what is telling the serving its default gateway is
> 192.168.2.1.
>
> Tony
Ouch... First of all, the server MUST have a static IP address and not
configured for DHCP. I would suggest to choose an easy, round number to
remember, such as 192.168.2.10.
Provide the following for the configuration (with the IP I suggested):
IP = 192.168.2.10
Mask = 255.255.255.0
Gateway = 192.168.2.1
DNS = 192.168.2.10
WINS = 192.168.2.10
Disable the outside NIC.
The above suggestions are based on the fact that the internal interface is
using the Belkin router as the Internet "edge' device, meaning that is what
is giving your network internet access. However, the way you have the SBS
configured with it's additional NIC (the 70.247.109.31 address), is
confusing.
Is there another router involved, or is the Belkin the only router?
Is the Belkin router configured for iternet access or is there another
router using the 70.247.109.31 address?
I would also suggest to disable DHCP on the Belkin router, and make the SBS
server the DHCP server. The wizard will assist to set it up. However, I
would suggest to disable the additional network card on the SBS and make the
connection as follows prior to running the wizard (from top to bottom, where
the top is the "Internet" or ATT).
ATT
^
ATT router/modem (configured in Bridge mode)
^
Belkin (bridged from the ATT router to use 70.247.109.31)
^
Switch (what the server and workstations are plugged into)
This way the Belkin is the internet connection using the ATT modem. How to
set it up in bridge mode would require you to call ATT for assistance. Tell
them you want it setup this way.
Otherwise, if you have a qualified technician that is familiar with SBS and
networking, he/she would be able to set this up very easily and quickly.
I also assume that you have port remaps that need to be configured, such as
80, 443, 4125 remapped to the SBS. However, if the Belkin supports UPnP, the
SBS wizard can configure it for you, but only after you configure the
network setup as outlined above in my mock diagram.
Take a look at the following pic to see what I mean about the whole setup.
Webtechie's infrastructure recommendation
http://s966.photobucket.com/albums/ae147/acefekay/Newsgroup%20Assistance/
Ace
Ace Fekay [MCT]
Sorry, this is the direct link to your pic:
http://i966.photobucket.com/albums/ae147/acefekay/Newsgroup%20Assistance/Webtechie.jpg
Ace Fekay [MCT]
news:uKdTpndf...@TK2MSFTNGP02.phx.gbl...
Darn, sorry about that - I had to make some changes at Photobucket.
Disregard the other two links. The direct link is now:
http://i966.photobucket.com/albums/ae147/acefekay/Newsgroup%20Assistance%20Visio%20Images/Webtechie.jpg
Ace
Webtechie
this is not working.
1) i disabled DHCP from the router
2) I enabled DHCP on the server
3) I ran the CEICW wizard
4) It wants to give the network connection the connection with the WAN IP
5) But the the local connection wants a static ip
6) the router did have a static ip. I moved that from the router to the
server.
7) Now nothing is working. I can't get on the internet.
8) I can't access the router.
Obviously, I did something wrong.
"Ace Fekay [MCT]" wrote:
> .
>
Ace Fekay [MCT]
> Ok, real confused here.
>
> this is not working.
>
> 1) i disabled DHCP from the router
> 2) I enabled DHCP on the server
> 3) I ran the CEICW wizard
> 4) It wants to give the network connection the connection with the WAN IP
> 5) But the the local connection wants a static ip
> 6) the router did have a static ip. I moved that from the router to the
> server.
> 7) Now nothing is working. I can't get on the internet.
> 8) I can't access the router.
>
> Obviously, I did something wrong.
>
I'll need to see a diagram or pic of exactly which cards are connected to
what device.
If you notice my diagram, I show the SBS with the "outside" NIC disabled,
and the "internal" NIC connected to the main switch that all otehr machines
are connected to, including the Belkin router.
From what you are trying to do is a little more complex and would require an
additional switch or cross over cable to connect the internal NIC of the
router to the external NIC of the SBS, and then the internal NIC to the
internal switch. I assume the Belkin has the ISP's WAN address, therefore,
the 'external' NIC in what you are proposing, needs to have a different IP
range between it and the Belkin.
However, when you posted your ipconfig, it appears your server has the ISP's
address, so honestly I do not understand exactly how the Belkin is
connected.
If you can draw how your SBS, router and workstations are connected
together, that would greatly help to understand what you have, and draw out
what you are trying to accomplish to provide specific help.
Ace
Webtechie
I've run the wizard, but it wants me to move the static ip address from the
router to the server.
I'm not sure what to do next, but the server can't see the clients. The
clients can't see the server, which means my application is down.
Tony
"Duncan McC" wrote:
> .
>
Ace Fekay [MCT]
> Duncan,
>
> I've run the wizard, but it wants me to move the static ip address from
> the
> router to the server.
>
> I'm not sure what to do next, but the server can't see the clients. The
> clients can't see the server, which means my application is down.
>
> Tony
>
Can you provide a detailed network diagram?
Ace
Duncan McC
attached to each point.
It shouldn't want to *move* the IP - rather than just copy it (so that
NIC is attached to the router). That should be the WAN/Internet NIC.
The internal NIC should be, um, internal - as far as IP's go.
So like...
* ISP
123.123.123
* Router - DHCP *disabled*
* Internet side NIC (TCP only enabled protocol)
IP might be 123.123.123 also (depends on your router setup)
importantly though: DNS server is SBS's - eg. 192.168.1.2
* Internal NIC (SBS side)
IP: 192.168.1.2
DNS: 192.168.1.2
The wizard should do most of that for you. It will do all of it for
you, *if*:
a) you have the router setup correctly! :)
b) (optional, but may help a) - you enable uPNP on the router (not
recommended by most here, but you are welcome to give it a go, IMO - you
can always turn it off and configure it manaully if uPNP causes grief).
(ie if you have a uPNP capable and enabled router, the wizard *might*
(should) configure the router for you). I never use it myself, but in
your case, it may help - as said you can turn it off if it writes bad
settings to the router - and configure it manually.
--
Duncan.
In article <C91EBBBA-E137-45B1...@microsoft.com>,
Webt...@discussions.microsoft.com says...
Webtechie
experience.
1) I ran the CEICW wizard and everything crashed!!!!
1a) First, the wireless NIC in the server was enabled (why a server would
have a wireless card is another issue altogether), it was given a public IP
address, and it was identified as the INTERNAL network interface.
1b) Second, the wired connection in the server was changed from a static IP
to DHCP so it pulled an address from the router, it was identified as the
EXTERNAL network connection, resulting in the server actively refusing all
connections from the 192.168.2.x network range because the server thought it
was the external network and by default no traffic from the external network
is allowed in.
1c) I was able to get the network configuration set correctly on the server
(disabling the wireless NIC, setting the wired NIC as the internal network
connection), but the Routing and Remote Access Service configuration that had
been set when the above network configuration was enabled was still blocking
all access from the 192.168.2.x network.
1d) We have an HP Switch which all clients were connected. Then we have a
Cisco router and a Belkin router. All that had to be troubleshooted and now
is the way it needed to be. I inherited this monster without really
understanding the diagram or flow of everything as ACE already mentioned.
1e) Once I was able to eliminate all other possible causes of network
blockage and find the RRAS service, I disabled it (which is normal in a
single-NIC SBS server configuration) and all access from the local
workstations to the server was restored.
1f) After the settings and all were properly configured. The clients
couldn't not connect to the domain. I had a SBS consultant on the phone
looking at everything with me. He must have got someone or a resource or
something because he figured out the RRAS service was the culprit. When I
ran the CEICW wizard, it started the RRAS service which locked the clients
out. Disabling that got me up and running.
2) The original problem of the long logons was due to use DHCP on the
router and not the SBS server. DHCP has now been set to the server. Of
course, the static IP was moved to the server.
3) I learned a lot about DNS forwards. I was keying that wrong in the
wizard. He went in and cleaned it up and took out the forwarders to the ISP
DNS servers. He told me SBS can do the work itself and didn't need those.
4) I was worked last night and early this morning to resolve the issue,
however, I was still was down this morning. I called the consultant that I
just happen to have recently met who is an expert on SBS and he was got right
to work. A little plug for Eriq Neale who literally wrote the book on SBS
(SBS 2003 and SBS 2008 Unleased).
5) We were down in production for two hours, but Neale got everything
configured properly.
Ace thanks for your help. Your jumping into was great and you were dead on
on several points that I didn't understand. However, when Neale was talking
to me, I remembered you had made similiar points. Thanks for creating the
diagram. I am going to do that now so that I can document this current
environment now that it is set up correctly.
Tony
"Ace Fekay [MCT]" wrote:
> .
>
Webtechie
outcome.
Tony
"Duncan McC" wrote:
> .
>
Ace Fekay [MCT]
Tony,
I'm very happy that you've found the problem with an SBS expert to assist.
Anything can become daunting, if you are not familiar with it, especially
SBS and all it's working parts.
You are welcome for the diagram. I created it in Visio, then saved it as a
JPG, then uploaded it to photobucket.com. Visio is a pretty good tool for
this sort of stuff, as well as other functions it performs.
Cheers!
Ace