Windows 2003 Server - Routing & Remote Access Problem

  • Thread starter Thread starter John Sanford
  • Start date Start date
J

John Sanford

Initially setup up the server to provide Internet
connectivity to private network, worked fine for several
days and ISP came and installed a new cable modem causing
server to no longer access the Internet.
New modem is unable to dynamically provide IP address,
tried doing a repair on Internet network adapter, but get
an error message saying that repair failed and a static
Ip has been assigned.
Any one had this problem and any solutions. Have
uninstalled RRAS and re-installed but no help.
 
Cable/DSL Router give out addresses,....modems do not. Modems don't even
have addresses themselves except for some "hybrid" models that some have
come out with lately. What do you really have?
 
The ISP service is on cable and the new cable modem is a
Motorola device, the system worked on the Arris device
befor it was swapped with the Motorola unit. The address
is dynamically provided by the cable company and usually
you can get it to cough up an IP by either removing power
from the device, repairing the network adaptor or both.
Thanks!
-----Original Message-----
Cable/DSL Router give out addresses,....modems do not. Modems don't even
have addresses themselves except for some "hybrid" models that some have
come out with lately. What do you really have?

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Initially setup up the server to provide Internet
connectivity to private network, worked fine for several
days and ISP came and installed a new cable modem causing
server to no longer access the Internet.
New modem is unable to dynamically provide IP address,
tried doing a repair on Internet network adapter, but get
an error message saying that repair failed and a static
Ip has been assigned.
Any one had this problem and any solutions. Have
uninstalled RRAS and re-installed but no help.


.
 
John Sanford said:
The ISP service is on cable and the new cable modem is a
Motorola device, the system worked on the Arris device
befor it was swapped with the Motorola unit. The address
is dynamically provided by the cable company and usually
you can get it to cough up an IP by either removing power
from the device, repairing the network adaptor or both.

I'm not sure, but that one might be one of those "hybrid" things (can't look
it up, you didn't give the model#). If it is supposed to give out IP# to
your machines and if it has a different subnet on the WAN side than what it
has on the LAN side then it is really a NAT Device. I guess it ain't bad
enough that these vedors butcher the dictionary by calling the most common
Cable/DSL NAT Devices "routers" but now they have to call them "modems" and
futher destroy the dictionary.

Anyway, aside from my "carrying on", I suspect that you may have a bad one
and they should try to replace it and see if that solves the problem. Also
keep in mind that there could be a PPPoE issue here as well that might
require software to be install somewhere for it to work. There isn't any
more I could think of to suggest about it.
 
Motorola calls it a Surfboard Cable Modem model #
SB5100. This device can be configured on an XP loaded
laptop and will work with it, but when moved to the
Win2003 Server it can't dynamiclly configure an IP.
Interesting note, we sometimes have to call the cable
company to reset the customer account to get the IP to
configure on the laptop. They act like this is the norm
for this device. Could this be the hybrid you mentioned?
I have never seen this before with this ISP's product!
Thanks!
John
-----Original Message-----


I'm not sure, but that one might be one of
those "hybrid" things (can't look
it up, you didn't give the model#). If it is supposed to give out IP# to
your machines and if it has a different subnet on the WAN side than what it
has on the LAN side then it is really a NAT Device. I guess it ain't bad
enough that these vedors butcher the dictionary by calling the most common
Cable/DSL NAT Devices "routers" but now they have to call them "modems" and
futher destroy the dictionary.

Anyway, aside from my "carrying on", I suspect that you may have a bad one
and they should try to replace it and see if that solves the problem. Also
keep in mind that there could be a PPPoE issue here as well that might
require software to be install somewhere for it to work. There isn't any
more I could think of to suggest about it.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


.
 
John Sanford said:
Interesting note, we sometimes have to call the cable
company to reset the customer account to get the IP to
configure on the laptop. They act like this is the norm
for this device.

So they are admiting it is a bunch of trouble, to the point that they almost
expect it?
Could this be the hybrid you mentioned?

It appears to be. The Ethernet port on it can support up to a maximum of 31
users,..that would be impossible without performing NAT, and that isn't
possible unless it is an "addressable" Layer3 Device because NAT is a
Layer3&4 function that depends on Layer3, therefore it is a NAT Device and
not simply a modem. Essentially it would be the same as any Cable Router but
without the "traditional" built-in 4 port switch.

Now that doesn't make it a "bad" product,...it is just another example of
the annoying "butchering" of the dictionary that I am always whinning about.
Things are a "modem" when they simply decide to call it that, and things are
a "router" when they simply decide to call it that,...and it doesn't seem to
matter what the devices *really* are based on what they actually *do*.

Anyway I suspect that this device is the root of your troubles. Maybe you
could check into using soemthing different, but you'll have to work with the
ISP since whatever you use must be able to work with thier system.
 
Back
Top