S
Saga
Hi all,
I am having a problem, most likely due to my lack of understanding on how
IPs are handled and used. I apologize for the long post, please bear with me.
If this is not the most appropriate ng to ask this, please let me know.
My setup consists of the following:
1. Small Business Server 2003, with DHCP server
2. 2 PCs, Win XP SP2
3. One Wifi notebook with Win 2000
4. One 5 port 10/100 switch
5. One wireless access point
The SBS2k3, two PCs and the WAP are connected to the switch.
All was well, then I contracted High Speed Cable Internet. This is where the
fun began. This is my first installation of this type, so although I consider
myself knowledgeable enough to set up a small LAN, I was nowhere near
prepared for this small addition.
I got out an old Linksys BEFSX41 router/firewall/VPN end point that I had. I
connected the cable modem to the router and then the router to the switch. Simple
enough. Note that I did not use the SBS2K3's Internet connectivity features
because this requires that the server contain 2 NICs and since this is a small
form factor PC, it only allows for one PCI expansion card.
When I thought I had everything running I discovered that I could not ping
an external web site, like www.amazon.com. I also discovered that my router
acted as a DHCP server. I wasn't sure what conflicts I could have by having 2
DHCP servers online. Also, my router insisted on giving out ips like 192.168.1.100
while the SBS2K3 server gave them out like 192.168.16.30. I changed this
in the router, so that it would also give out ips with the "16", but then opted to
disable this service completely. I also changed the default gateway which
pointed to the SBS2K3 so that it would point to the router. I was; however,
able to successfully ping the router and the cable modem.
This being done I still could not ping external web sites and after some experimentation
I discovered that my DNS server was also pointing to the SBS2K3, so I copied the DNS
servers that I was getting from the cable modem. Once that was done I was able to ping
external web sites. I restarted the XP PC and discovered to my horror that it was taking
about 5 minutes stuck on the pre login process "Applying computer settings". Finally,
when the login dialog appeared and I logged in, it took another 5 minutes stuck on the
"Applying personal settings" step. Finally, after an inordinate amount of time, the desktop
was ready to use. Since this did not happen when I changed the default gateway, I
assumed that the change in the DNS server was to blame. I added a third DNS server,
this being the SBS2K3's ip. I restarted (again) and this it booted like a charm, under a
minute (counting from the time the loader comes on till the desktop is ready to use).
However, the server's name is not being resolved correctly. I use Remote Desktop (RD)
to connect to the server for maintenance and shutdown and I have always used
the server's name to connect, like MINI-C. Yet after the last boot, RD could not find
the server; however, the process works perfectly if I substitute the server name for
its IP.
Basically, the only change I did to the original setup (besides the hardware addition) is
that I changed the default gateway to point to the router, disabled the DHCP server on
the router and added the two DNS server ips that I got from the cable modem, keeping
the original DNS server pointing to the SBS2K3.
So, after this long winded description comes my questions:
What am I missing so that the server's name is correctly resolved when I attempt to
connect to it through Remote Desktop? Does the order in which I defined the DNS servers
make a difference? Is there something else that I need to take into account for my current
setup (that is, connecting the setup described above to the Internet through a router and
cable modem)?
Thank you for your time and orientation.
Saga
I am having a problem, most likely due to my lack of understanding on how
IPs are handled and used. I apologize for the long post, please bear with me.
If this is not the most appropriate ng to ask this, please let me know.
My setup consists of the following:
1. Small Business Server 2003, with DHCP server
2. 2 PCs, Win XP SP2
3. One Wifi notebook with Win 2000
4. One 5 port 10/100 switch
5. One wireless access point
The SBS2k3, two PCs and the WAP are connected to the switch.
All was well, then I contracted High Speed Cable Internet. This is where the
fun began. This is my first installation of this type, so although I consider
myself knowledgeable enough to set up a small LAN, I was nowhere near
prepared for this small addition.
I got out an old Linksys BEFSX41 router/firewall/VPN end point that I had. I
connected the cable modem to the router and then the router to the switch. Simple
enough. Note that I did not use the SBS2K3's Internet connectivity features
because this requires that the server contain 2 NICs and since this is a small
form factor PC, it only allows for one PCI expansion card.
When I thought I had everything running I discovered that I could not ping
an external web site, like www.amazon.com. I also discovered that my router
acted as a DHCP server. I wasn't sure what conflicts I could have by having 2
DHCP servers online. Also, my router insisted on giving out ips like 192.168.1.100
while the SBS2K3 server gave them out like 192.168.16.30. I changed this
in the router, so that it would also give out ips with the "16", but then opted to
disable this service completely. I also changed the default gateway which
pointed to the SBS2K3 so that it would point to the router. I was; however,
able to successfully ping the router and the cable modem.
This being done I still could not ping external web sites and after some experimentation
I discovered that my DNS server was also pointing to the SBS2K3, so I copied the DNS
servers that I was getting from the cable modem. Once that was done I was able to ping
external web sites. I restarted the XP PC and discovered to my horror that it was taking
about 5 minutes stuck on the pre login process "Applying computer settings". Finally,
when the login dialog appeared and I logged in, it took another 5 minutes stuck on the
"Applying personal settings" step. Finally, after an inordinate amount of time, the desktop
was ready to use. Since this did not happen when I changed the default gateway, I
assumed that the change in the DNS server was to blame. I added a third DNS server,
this being the SBS2K3's ip. I restarted (again) and this it booted like a charm, under a
minute (counting from the time the loader comes on till the desktop is ready to use).
However, the server's name is not being resolved correctly. I use Remote Desktop (RD)
to connect to the server for maintenance and shutdown and I have always used
the server's name to connect, like MINI-C. Yet after the last boot, RD could not find
the server; however, the process works perfectly if I substitute the server name for
its IP.
Basically, the only change I did to the original setup (besides the hardware addition) is
that I changed the default gateway to point to the router, disabled the DHCP server on
the router and added the two DNS server ips that I got from the cable modem, keeping
the original DNS server pointing to the SBS2K3.
So, after this long winded description comes my questions:
What am I missing so that the server's name is correctly resolved when I attempt to
connect to it through Remote Desktop? Does the order in which I defined the DNS servers
make a difference? Is there something else that I need to take into account for my current
setup (that is, connecting the setup described above to the Internet through a router and
cable modem)?
Thank you for your time and orientation.
Saga