Google Answers Logo
View Question
 
Q: TCP/IP Networking Stumper Windows XP (?) TCP-IP ( No Answer,   4 Comments )
Question  
Subject: TCP/IP Networking Stumper Windows XP (?) TCP-IP
Category: Computers > Operating Systems
Asked by: froschatten-ga
List Price: $50.00
Posted: 24 Aug 2003 14:26 PDT
Expires: 25 Aug 2003 05:53 PDT
Question ID: 248285
I'm trying to network a shared Starband satellite modem connection,
and I've run into a problem setting up a print server on a Netgear
FM114P router that has a built-in print server. The way a Starband
satellite modem works, I cannot connect it directly to a router. I
have to connect it to a host PC. This host PC acts as a gateway. Then
I can connect a router to an Ethernet card in the gateway (host) PC,
and connect client workstations to the router.

My gateway PC is a Dell minitower running Windows XP Professional. It
has two Ethernet cards. The first is a built-in 3Com, and the second
is a Netgear PCI card I installed in an available slot.

The Starband satellite modem is assigned an IP address by the Starband
network. Let's say the IP address of the modem is 148.63.X.X. The
modem connects to the first Ethernet card in the PC, and the modem
acts as a DHCP server to the gateway PC. It assigns the first Ethernet
card an IP address of 192.168.1.X.

The router connects to the second Ethernet card in the PC, and I
manually assigned the router an IP address of 192.168.0.X. The two
Ethernet cards in the gateway PC communicate through ICS. The router
acts as a DHCP server to attached client PCs.

Client PCs attached to the router can ping the router.
Client PCs attached to the router can ping the gateway PC.
When I'm at the gateway PC, I cannot ping the router.

I have to be able to see the router from the gateway PC because the
gateway PC has to act as a spooler for the router's print server.

Any thoughts?

Thank you.
Answer  
There is no answer at this time.

Comments  
Subject: Re: TCP/IP Networking Stumper Windows XP (?) TCP-IP
From: funkywizard-ga on 24 Aug 2003 20:15 PDT
 
I'm not really understanding the necessity of the router in this
configuration. Couldn't you just attach the printer to the gateway pc?
Or if you want to use the router for it's print serving capabilities,
how do you have all the computers connected to it? Is the gateway pc
connected to the wan port with the other pc's connected to the lan
port? If that is the case, it is of little surprise to me that the
gateway computer cannot ping the router, or print to it, since under
common configurations, doing so would allow anyone on the internet to
print to your printer.

Depending on the setup you have, it may be some simple
mis-configuration, but I'm afraid I'm having a hard time following
exactly what you have setup and why, which makes it difficult for me
to troubleshoot. Any light you could shed on this would help me get to
the root of your problem.
Subject: Re: TCP/IP Networking Stumper Windows XP (?) TCP-IP
From: kevan-ga on 24 Aug 2003 21:06 PDT
 
While I don't understand the need for the router in this config, I
think the problem is the default ip address ranges that ICS and the
router are using.  If the router and ICS are using the same IP
networks, the workstations will not be able to route the packets
properly.

I would let the router DHCP an address from the ICS workstation and
have the router hand out DHCP leases on 10.10.0.0.

Kevan
Subject: Re: TCP/IP Networking Stumper Windows XP (?) TCP-IP
From: funkywizard-ga on 24 Aug 2003 22:37 PDT
 
I agree that this looks a bit like an IP address, subnet, or other
routing related misconfiguration. However, with the information given
on how the network is set up, it is impossible to be sure exactly what
the problem is at this point.
Subject: Re: TCP/IP Networking Stumper Windows XP (?) TCP-IP
From: chuypalma-ga on 25 Aug 2003 00:44 PDT
 
My two routers (US Robotics and SMC) have the option to "Discard PING
from WAN side" and since your gateway PC is on the WAN side, that may
be the reason you can't ping it.
Also, neither router requires a PC to act as a print spooler, but in
case the Netgear FM114P does (which I doubt from reading their
documentation), it would have to be located on the LAN side.
I also agree with funkywizard-ga that the WAN side does not (and
should not) allow printing, but don't forget you usually have to run
some software on each of the LAN PC's to be able to print to a network
printer, which appears as a new type of port (LPT1, LPT2, PRTmate).
Your choice of IP's is correct, but incomplete (192.168.1.X for the
satellite modem and the gateway PC, 192.168.0.X for the second
Ethernet card in the gateway PC and the WAN port on the router, and
192.168.2.X for the DHCP server in the Netgear router).  Don't forget
you have TWO DHCP servers, one in the modem and the other in the
Netgear router.
Good luck.

Important Disclaimer: Answers and comments provided on Google Answers are general information, and are not intended to substitute for informed professional medical, psychiatric, psychological, tax, legal, investment, accounting, or other professional advice. Google does not endorse, and expressly disclaims liability for any product, manufacturer, distributor, service or service provider mentioned or any opinion expressed in answers or comments. Please read carefully the Google Answers Terms of Service.

If you feel that you have found inappropriate content, please let us know by emailing us at answers-support@google.com with the question ID listed above. Thank you.
Search Google Answers for
Google Answers  


Google Home - Answers FAQ - Terms of Service - Privacy Policy