Windows Forum

Ask something
Discussion Locked

Actually its Two Questions...

0 helpful
8 replies

by mrdbcooper 3 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

A little background first, the network is
running NT 4.0 Server with SP3 on an Intel
Petium Pro 200 as a PDC. This server is also running MS Backoffice 4.0. The new server (which we wish to replace the old one with) is a dual pentium III 600 running NT 4.0 SP 4 with MS Backoffice 4.5.

Now the questions, one the new server we wish to run Cable (Time-Warner) to use as the web connection for ten workstations.
Now we already have run into the DHCP problems of Backoffice and the TW cable.
Weworked around that vis a linksys cable router. Now what we need is to set up the new server to serve any units that need to be connected to the cable. So far using Linksys DHCP has failed and using Backoffice DHCP has failed and signing static addressing of TCP/IP failed as well. What is the Network Admin doing wrong????
Also how can we remove BackOffice 4.0 off of the old server without a re-install of NT???

8 replies

by falvarado

Although I would need a bit more information to accuratly answer this, I will assume that the PDC, which is acting as a Gateway is a multi-homed system. Also, you do not state what kind of addressing is required for your internal network (valid address vs. RFC 1918 "invalid" address)which could make the solution a bit different (i.e NAT & Routing vs. just Routing).

In either which case, I would make the PDC the DHCP server to handle the internal workstations. You would also consider installing RRAS (Routing on RAS) to utilize the routing functions of that service from your internal network to the cable provider. Also, ensure that IPForwarding is selected on the NT box in the TCP/IP properties.

Sorry if this sounds a bit vague, but with more information, I'm sure someone will give you a better answer than me :)

by mrdbcooper

At present MS Backoffice 4.0 is using DHCP to assign dynamic IP address to all workstations and printers.
We have tried to set fixed IP addresses to all the units and have disabled the DHCP server on the PDC. This produced no solution when it came to then using the Linksys Cable Router as a DHCP system. Now the TW Cable automatically (due to the nature of the service we signed up for) generates a dynamic IP address from the cable modem to the Linksys. We have tried to get the linksys to take that IP and use it, then assign the other workstations IP's based off of the linksys starting IP address through DHCP. This has not worked to provide service to the other workstations. (BTW we also disabled the Internet Services of Backoffice so as not to have it interfere - still no dice)
The idea is to get access to the internet services to the workstations and leaving only a DMZ IP for any telecommuting coming across the net.
So far we have had no success.
As for your question of addressing that would be something I would leave to the consulting NT folks. But I can bet you dollars to doughnuts as they are not NT certified, they would not have a clue what addressing is being used. So the answer would be whatever defaults from MS Backoffice 4.0 concerning RAS and DHCP.

Thanks for at least answering!

by Former member

You do need a consultant..Your description is confusing and you haven't provided crucial information such as: IP addresses leased? Or internal only? Need NAT then, or proxy...

Router has an IP address, did Time-Werner give you a group of IP addresses then for the rest of your network to use? If so, then it is simple. If not, more difficult.

Your DHCP problems, you have not described the problems at all. You need scopes for DHCP and you need to know how to configure IP subnets.

Backoffice is for apps such as Exchange, SQL Server...etc. Has nothing to do with DHCP, which comes with NT4 Server. If you want SQL Server, Exchange...etc on you other new server, then you'll need the B.O. CD.

by mrdbcooper

IP Address from TW is a dynamic IP. The workstation IP's are also dynamic based on the Linksys starting IP address and going to up. Have tried fixed IP's that we set manually based off the Linksys router with no resolution of problem. We are using MS Proxy and that is part of the problem. Contacted MS and they suggested the disabling of ALL Backoffice use of DHCP and Proxy. Still to no avail.
Backoffice defaults to using DHCP and that is why it is NOT usable with the TW which also uses DHCP. We do not plan ever using exchange but will be using SQL 7.0 from the new pack. But that is neither here nor there as SQL will run without Backoffice.
I suppose the REAL problem is Backoffice itself, but this is what our current network consultants recommended.

by ronnonf

You should implement some type of NAT routing. Do not use the Linksys router for DHCP. NAt can be done either with MS Proxy (I believe) Win2k, or Symantec makes software to help.
It might sound wierd, but go to a site called www.dslreports.com. Then go to the tools or links options this should show you a number of NAT packages.
As per Removing BO I believe the only way if to hack the registry. This was written up in a MS doc.

by mrdbcooper

Went to the site and found no real useful information on NAT.
And as for Win2000, that is right out as
we are using NT 4.0

by mrdbcooper

We have a solution for the situation of the Dynamic IP address to a SBS server and here it is:

On the issue of the Time Warner cable, Linksys Cable Router, and Small Business Server.

Connect the cable to the router and configure the router from its default address
to the first default address range of SBS's installation.

Disable the DHCP function of the router.

On the SBS server, reconfigure the IP for
the server to be the second IP in the default range of SBS's installation.
(ex. if the range is 100.0.0.1 - 100.0.0.255
then the router is 100.0.0.1 and the server
is 100.0.0.2) add the DNS from Time Warner
in your search order.

Use the DHCP server on the SBS and go into
the manager and make static the IP's of the default range. Each network device receiving
and specified IP address.

Make sure that each device will receive IP
leases through DHCP and there you have it.

Thanks for everyone's fix. They all eventually leaded us into the right direction!

This discussion is closed to new replies.