All,
Recently purchased a new 2008 server. I added this new server to our SBS
2003 environment. I was able to JOIN the sbs domain. My problem now is that
I can not ping the sbs box or any other TS server on the network.

I assigned the new server the following IP information:
IP address: 192.168.1.11
Mask: 255.255.255.0
Gateway: 192.168.1.1
DNS 192.168.1.2 (this is the SBS box)

Our SBS box is using one NIC card. We have a router that is handling our
firewall.

Thank you,

Thomas

"Thomas Kroljic" <tkroljic@newsgroup> wrote in message news:Oa$tf%2382KHA.5196@newsgroup

> All,
> Recently purchased a new 2008 server. I added this new server to our SBS
> 2003 environment. I was able to JOIN the sbs domain. My problem now is that
> I can not ping the sbs box or any other TS server on the network.
>
> I assigned the new server the following IP information:
> IP address: 192.168.1.11
> Mask: 255.255.255.0
> Gateway: 192.168.1.1
> DNS 192.168.1.2 (this is the SBS box)
>
> Our SBS box is using one NIC card. We have a router that is handling our
> firewall.
>
> Thank you,
>
> Thomas
>
>

Have you tried disabling all 3 sections of the Windows Firewall on 2008? Try that, and ping again. You can customize the firewall (usually just the "Domain" firewall) to allow ICMP Echo, which is what a simple ping uses.

Can other machines ping 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, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

Ace,
The other two Terminal Servers can ping the SBS box. They have been in
production for several years. I will try your suggest to disable all the
firewalls and then ping the sbs box. Do I need to reboot the server after
changing the firewall settings?
Disabling the firewall settings on the new 2008 server, won't this open
the box up to trouble?

Thanks,

"Ace Fekay [MVP-DS, MCT]" <aceman@newsgroup> wrote in message
news:eFpWci%232KHA.5820@newsgroup
"Thomas Kroljic" <tkroljic@newsgroup> wrote in message
news:Oa$tf%2382KHA.5196@newsgroup

> All,
> Recently purchased a new 2008 server. I added this new server to our SBS
> 2003 environment. I was able to JOIN the sbs domain. My problem now is
> that
> I can not ping the sbs box or any other TS server on the network.
>
> I assigned the new server the following IP information:
> IP address: 192.168.1.11
> Mask: 255.255.255.0
> Gateway: 192.168.1.1
> DNS 192.168.1.2 (this is the SBS box)
>
> Our SBS box is using one NIC card. We have a router that is handling our
> firewall.
>
> Thank you,
>
> Thomas
>
>

Have you tried disabling all 3 sections of the Windows Firewall on 2008? Try
that, and ping again. You can customize the firewall (usually just the
"Domain" firewall) to allow ICMP Echo, which is what a simple ping uses.

Can other machines ping 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, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.

"Thomas Kroljic" <tkroljic@newsgroup> wrote in message news:uKSUEJC3KHA.5212@newsgroup

> Ace,
> The other two Terminal Servers can ping the SBS box. They have been in
> production for several years. I will try your suggest to disable all the
> firewalls and then ping the sbs box. Do I need to reboot the server after
> changing the firewall settings?
> Disabling the firewall settings on the new 2008 server, won't this open
> the box up to trouble?
>
> Thanks,
>

No reboot required. No, it won't open it to trouble. Let's try it for testing purposes, please, to see if this is the cause. You can always re-enabled it afterwards, but creating rules to all ICMP Echo. But honestly, if it is part of a domain, the domain portion of the firewall should allow ICMP Echo.

Ace

Ace,
I'll try changing the Firewall settings this weekend and post the
results back here.

"Ace Fekay [MVP-DS, MCT]" <aceman@newsgroup> wrote in message
news:%2374RkbK3KHA.3728@newsgroup
"Thomas Kroljic" <tkroljic@newsgroup> wrote in message
news:uKSUEJC3KHA.5212@newsgroup

> Ace,
> The other two Terminal Servers can ping the SBS box. They have been in
> production for several years. I will try your suggest to disable all the
> firewalls and then ping the sbs box. Do I need to reboot the server after
> changing the firewall settings?
> Disabling the firewall settings on the new 2008 server, won't this open
> the box up to trouble?
>
> Thanks,
>

No reboot required. No, it won't open it to trouble. Let's try it for
testing purposes, please, to see if this is the cause. You can always
re-enabled it afterwards, but creating rules to all ICMP Echo. But honestly,
if it is part of a domain, the domain portion of the firewall should allow
ICMP Echo.

Ace

"Thomas Kroljic" <tkroljic@newsgroup> wrote in message news:OOkiQnW3KHA.556@newsgroup
Sounds good!

Ace

> Ace,
> I'll try changing the Firewall settings this weekend and post the
> results back here.
>
> "Ace Fekay [MVP-DS, MCT]" <aceman@newsgroup> wrote in message
> news:%2374RkbK3KHA.3728@newsgroup
> "Thomas Kroljic" <tkroljic@newsgroup> wrote in message
> news:uKSUEJC3KHA.5212@newsgroup

>> Ace,
>> The other two Terminal Servers can ping the SBS box. They have been in
>> production for several years. I will try your suggest to disable all the
>> firewalls and then ping the sbs box. Do I need to reboot the server after
>> changing the firewall settings?
>> Disabling the firewall settings on the new 2008 server, won't this open
>> the box up to trouble?
>>
>> Thanks,
>>

>
>
> No reboot required. No, it won't open it to trouble. Let's try it for
> testing purposes, please, to see if this is the cause. You can always
> re-enabled it afterwards, but creating rules to all ICMP Echo. But honestly,
> if it is part of a domain, the domain portion of the firewall should allow
> ICMP Echo.
>
> Ace
>
>

Ace,
I went into the firewall options on the 2008 server and turned off each
firewall. I'm still unable to ping the SBS box. I noticed that I wasn't even
able to ping the gateway (192.168.1.1). Not sure why this is.

I tried the following:

I disconnected the server from the SBS domain. Rebooted. I then changed
the NIC card settings
so the IP address would come from the DHCP but I left the DNS setting alone
(it still points to the sbs box which is 192.168.1.2).

I then rejoined the Domain. After joining the domain, I was able to ping
the SBS server. But, if I go into the NIC card on the 2008 server and change
the IP address to
IP address 192.168.1.11
Mask 255.255.255.0
Gateway 192.168.1.1
DNS 191.168.1.2

after this change I am then unable to ping the SBS box. Go figure!

Any suggestions.

"Ace Fekay [MVP-DS, MCT]" <aceman@newsgroup> wrote in message
news:%23Hl5u$X3KHA.1660@newsgroup

"Thomas Kroljic" <tkroljic@newsgroup> wrote in message
news:OOkiQnW3KHA.556@newsgroup
Sounds good!

Ace

> Ace,
> I'll try changing the Firewall settings this weekend and post the
> results back here.
>
> "Ace Fekay [MVP-DS, MCT]" <aceman@newsgroup> wrote in
> message
> news:%2374RkbK3KHA.3728@newsgroup
> "Thomas Kroljic" <tkroljic@newsgroup> wrote in message
> news:uKSUEJC3KHA.5212@newsgroup

>> Ace,
>> The other two Terminal Servers can ping the SBS box. They have been in
>> production for several years. I will try your suggest to disable all the
>> firewalls and then ping the sbs box. Do I need to reboot the server after
>> changing the firewall settings?
>> Disabling the firewall settings on the new 2008 server, won't this open
>> the box up to trouble?
>>
>> Thanks,
>>

>
>
> No reboot required. No, it won't open it to trouble. Let's try it for
> testing purposes, please, to see if this is the cause. You can always
> re-enabled it afterwards, but creating rules to all ICMP Echo. But
> honestly,
> if it is part of a domain, the domain portion of the firewall should allow
> ICMP Echo.
>
> Ace
>
>

"Thomas Kroljic" <tkroljic@newsgroup> wrote in message news:ublZsFk3KHA.3728@newsgroup

> Ace,
> I went into the firewall options on the 2008 server and turned off each
> firewall. I'm still unable to ping the SBS box. I noticed that I wasn't even
> able to ping the gateway (192.168.1.1). Not sure why this is.
>
> I tried the following:
>
> I disconnected the server from the SBS domain. Rebooted. I then changed
> the NIC card settings
> so the IP address would come from the DHCP but I left the DNS setting alone
> (it still points to the sbs box which is 192.168.1.2).
>
> I then rejoined the Domain. After joining the domain, I was able to ping
> the SBS server. But, if I go into the NIC card on the 2008 server and change
> the IP address to
> IP address 192.168.1.11
> Mask 255.255.255.0
> Gateway 192.168.1.1
> DNS 191.168.1.2
>
> after this change I am then unable to ping the SBS box. Go figure!
>
> Any suggestions.
>

After changing it, does it resolve when you try to ping, but you just don't receive replies?

How about nslookup? Does that work when trying go resolve something, anything, - try resolving the SBS server FQDN, as well as something outside, such as www.intel.com.

It's starting to sound like the SBS domain GPO firewall, or the .11 address is in conflict with something else being used. What is the current DHCP scope range?



Ace

Ace,

Do you know where in the SBS 2003 box I would go to remove any reference to
the new server's IP address? If I disjoin the domain, and I go to the SBS
2003 box and ping the 192.168.1.11 address, it still tries to locate the
FQDN address of the new 2008 server even though it doesn't belong to the
domain. So, since I'm not a OS guy, where would I go to remove all
references to the 192.168.1.11 address that was used by the new 2008 server?

I went under the DNS application and anything that had the 192.168.1.11
address I deleted. But it still seems to want to resolve the name (I
originally named the new 2008 server has follows when I joined the sbs
domain: 1718Server)

Additional information:
We have some new routes that another company installed and maintains.
This was done to handle our new T1 Phone Lines. This same equipment is now
used for data. Anyway, it appears that after a complete reinstall of the
2008 OS on the new server, I noticed that the box gets the following
addresses assigned to the NIC card:
IP address 192.168.101.36
mask 255.255.255.0
Gateway 192.168.101.1
DHCP 191.168.101.1
DNS 4.4.2.2 (free dns)

with these setting I can get out to the Internet and also ping the SBS box
via the 192.168.1.2

I changed the DNS to 192.168.1.2 for testing. When I go this, I can ping the
SBS box via the server name. I can also join the SBS domain without a
problem. After joining the domain, I can ping the SBS box with either the IP
address or FQDN.
Now, if I assign the IP addresses on the NIC card in the 2008 server to :
IP address 192.168.1.11
mask 255.255.255.0
Gateway 192.168.1.1
and leave the DNS at 192.168.1.2

With this change, I can not ping the SBS box or even get out to the
Internet. Even after Disabling all the firewalls on the 2008 server.




"Ace Fekay [MVP-DS, MCT]" <aceman@newsgroup> wrote in message
news:O3cQDxk3KHA.1452@newsgroup

"Thomas Kroljic" <tkroljic@newsgroup> wrote in message
news:ublZsFk3KHA.3728@newsgroup

> Ace,
> I went into the firewall options on the 2008 server and turned off each
> firewall. I'm still unable to ping the SBS box. I noticed that I wasn't
> even
> able to ping the gateway (192.168.1.1). Not sure why this is.
>
> I tried the following:
>
> I disconnected the server from the SBS domain. Rebooted. I then changed
> the NIC card settings
> so the IP address would come from the DHCP but I left the DNS setting
> alone
> (it still points to the sbs box which is 192.168.1.2).
>
> I then rejoined the Domain. After joining the domain, I was able to ping
> the SBS server. But, if I go into the NIC card on the 2008 server and
> change
> the IP address to
> IP address 192.168.1.11
> Mask 255.255.255.0
> Gateway 192.168.1.1
> DNS 191.168.1.2
>
> after this change I am then unable to ping the SBS box. Go figure!
>
> Any suggestions.
>

After changing it, does it resolve when you try to ping, but you just don't
receive replies?

How about nslookup? Does that work when trying go resolve something,
anything, - try resolving the SBS server FQDN, as well as something
outside, such as www.intel.com.

It's starting to sound like the SBS domain GPO firewall, or the .11 address
is in conflict with something else being used. What is the current DHCP
scope range?



Ace

On Sat, 17 Apr 2010 16:03:02 -0400, "Thomas Kroljic"
<tkroljic@newsgroup> wrote:

>Ace,
>
>Do you know where in the SBS 2003 box I would go to remove any reference to
>the new server's IP address? If I disjoin the domain, and I go to the SBS
>2003 box and ping the 192.168.1.11 address, it still tries to locate the
>FQDN address of the new 2008 server even though it doesn't belong to the
>domain. So, since I'm not a OS guy, where would I go to remove all
>references to the 192.168.1.11 address that was used by the new 2008 server?

You would check in two places - DNS and WINS, that is if WINS is
installed, however, I didn't see it in the ipconfig you provided, but
then again the ipconfig appeared to be manually typed in instead of
copied and pasted from the command prompt.

>
>I went under the DNS application and anything that had the 192.168.1.11
>address I deleted. But it still seems to want to resolve the name (I
>originally named the new 2008 server has follows when I joined the sbs
>domain: 1718Server)
>
>Additional information:
> We have some new routes that another company installed and maintains.
>This was done to handle our new T1 Phone Lines. This same equipment is now
>used for data. Anyway, it appears that after a complete reinstall of the
>2008 OS on the new server, I noticed that the box gets the following
>addresses assigned to the NIC card:
> IP address 192.168.101.36
> mask 255.255.255.0
> Gateway 192.168.101.1
> DHCP 191.168.101.1
> DNS 4.4.2.2 (free dns)
>
>with these setting I can get out to the Internet and also ping the SBS box
>via the 192.168.1.2

Apparently the Gatway is your DHCP server, and where it's getting the
DNS address now. If you are not already aware of it, you must only use
the current domain's DNS server for a DNS address. Otherwise expect AD
issues. For example, if you using 4.4.2.2, how is anything supposed to
"find" AD, including the server itself (since the server itself is
also a DNS client)?

>
>I changed the DNS to 192.168.1.2 for testing. When I go this, I can ping the
>SBS box via the server name. I can also join the SBS domain without a
>problem. After joining the domain, I can ping the SBS box with either the IP
>address or FQDN.
>Now, if I assign the IP addresses on the NIC card in the 2008 server to :
> IP address 192.168.1.11
> mask 255.255.255.0
> Gateway 192.168.1.1
> and leave the DNS at 192.168.1.2
>
> With this change, I can not ping the SBS box or even get out to the
>Internet. Even after Disabling all the firewalls on the 2008 server.
>
>

Then this appears to be a block on the edge firewall (the router to
the internet). Either that, or it cannot handle EDNS0, (DNS UPD
packets larger than 512 bytes), or there is a Root zone installed on
the DNS server (it's a zone that looks like a period).

Is a Forwarder configured in DNS properties, Forwarders tab? You can
use 4.2.2.2 as a Forwarder.
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, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.