Re: Cannot Ping

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Do you also have a route to your B subnet on the SBS server (or on your temp
GW) pointing to 5 (your router)? Did you change the DNS on the server in the
B subnet to your SBS DNS?

"Brian" <b_houghtby@xxxxxxxxxxxxx> wrote in message
news:QiW%g.19320$UG4.8737@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
OK ... I added a gateway to the SBS of 192.168.0.1, which is my temporary
gateway and now I can ping everything. I still cannot join the 03 server
at location B to the SBS at location A Domain. My first experience with a
domain.


"cjobes" <cjobes@xxxxxxxxxxxxx> wrote in message
news:OKcXIyK%23GHA.4704@xxxxxxxxxxxxxxxxxxxxxxx
Ok Brian, I read through the whole thread again, trying to get the
picture here. I can't see any way your computers can talk to a DNS or a
WINS in your local network. The lack of a ping response could be a
firewall on the server.

Let's focus on the B subnet first. I need some clarification. What
hardware has the IP address 147 and what hardware has the IP address 1?
Where did you get the DNS IP addresses from? Is the B subnet a workgroup?
How are the computers and the server connected? Switch? what kind?

Once we clear up the B subnet we can work on your A subnet.

Claus


"Brian" <b_houghtby@xxxxxxxxxxxxx> wrote in message
news:fNU%g.12938$Lv3.1854@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


Windows IP Configuration



Host Name . . . . . . . . . . . . : bhoughtby

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Mixed

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection

Physical Address. . . . . . . . . : 00-50-8D-75-56-BD

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.2.127

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.1

DHCP Server . . . . . . . . . . . : 192.168.2.149

DNS Servers . . . . . . . . . . . : 24.95.80.41

24.95.80.45

Lease Obtained. . . . . . . . . . : Wednesday, October 18, 2006
12:14:47 PM

Lease Expires . . . . . . . . . . : Monday, July 13, 2009
12:14:47 PM



Windows IP Configuration



Host Name . . . . . . . . . . . . : SERVER5

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection 2:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Intel(R) PRO/1000 EB Network
Connection with I/O Acceleration #2

Physical Address. . . . . . . . . : 00-15-17-0E-F8-5B



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/1000 EB Network
Connection with I/O Acceleration

Physical Address. . . . . . . . . : 00-15-17-0E-F8-5A

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.2.10

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 24.95.80.41

24.95.80.45



"cjobes" <cjobes@xxxxxxxxxxxxx> wrote in message
news:eGoqf6H%23GHA.2408@xxxxxxxxxxxxxxxxxxxxxxx
Post an ipconfig from that server and one of the workstations at the b
location.

"Brian" <b.houghtby@xxxxxxxxxxxxxxxx> wrote in message
news:o8Q%g.18758$pq4.8501@xxxxxxxxxxxxxxxxxxxxxxxxx
OK ... This is strange. I cannot even ping the 2003 server from a
workstation on the same subnet at location b. Appears this server is
unreachable from any machine, even on the same LAN!

What am I missing!?!

"Brian" <b.houghtby@xxxxxxxxxxxxxxxx> wrote in message
news:x0J%g.18630$pq4.4457@xxxxxxxxxxxxxxxxxxxxxxxxx
I have 2 locations tied together with a frame relay circuit. The 2
locations are on 2 separate subnets, Location A is 192.168.0.xxx and
location B is 192.168.2.xxx. Our internet connect is at location A as
is our mail server. The computer that hosting our mail and sharing
the Internet connection is just an XP pro machine with 2 NICS in it.

I am replacing this xp pro machine with sbs 03 premium and
implementing a "Real" DHCP server, exchange and faxing service. I
have to do a route add on the current xp pro machine to get it to
talk to location b. I think this just adds something like a next hop
to the box. For some reason I cannot get the new sbs03 server to
ping the 03 server at location b or vice-versa. I can, however ping a
workstation at location b from the sbs03 at location a. Any
suggestions to try?

Thanks!
Brian













.



Relevant Pages

  • Re: Cannot connect client to server 2003
    ... you need to reconfigure the IP schema of your SBS ... On the SBS 2003 Server open the Server Management console. ... On the Connection Type page, click Broadband, and then click Next. ... Alternate DNS server, type the IP addresses that are provided by your ISP ...
    (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: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Anyway the Server Ipconfig /all is this... ... Server Local Area Connection: ... Les Connor [SBS Community Member - SBS MVP] ... First Page of the Internet Connection Wizard, ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)