Hiya, thanks for your response.
Ive had printers that worked on the 2.2.2.x subnet which worked till 3
weeks ago.
my DC worked as the printer server as 1.1.1.2
Another thing I found out last night:
When I put a machine in the 2.2.2.x range then it can ping the 1.1.1.x
ips, but not the other way around. DNS isnt working either. The only
thing that can be resolved is the 1.1.1.2(DC/DNS server).
I checked in our default gateway(router) and the subnets are added.
So there is a connection, but its just one way....
Best regards
Dead
Bill Grant wrote:
> OK. Your ISP has given you a number of public IP addresses. There isn't
> really any way that you can use these addresses on your local LAN (which I
> presume is using private IP addresses).
>
> The usual procedure is to use one machine as a NAT device between your
> private LAN and the Internet. You can use a hardware device or a server
> running RRAS or ISA server (or third party firewall software). You allocate
> the pool of public IP addresses to this device and program it to map public
> IPs to machines on the private LAN. Do NOT try to use a DC for this purpose.
>
>
> Dead wrote:
> > My isp has given it to me. So I havent done anything yet. But so far
> > its only 1 NIC in the DC.
> >
> > /Dead
> >
> > Bill Grant skrev:
> >
> >> How has this new subnet been added? Have you put two NICs in the DC,
> >> one in each subnet? This is not a good idea.
> >>
> >>
> >> Dead wrote:
> >>> Hello,
> >>>
> >>> I have the subnet 1.1.1.1 with the mask 255.255.255.192, now Ive
> >>> been given a new subnet 2.2.2.2 with the mask 255.255.255.224. When
> >>> I give my printer servers an ip in the 2.2.2.2 range then the pcs
> >>> on the
> >>> 1.1.1.x range cant reach them, nor ping them.
> >>>
> >>> Changing the mask is not an option unfortunately, should I add a
> >>> route or something? Please help
> >>>
> >>> How do I fix this in my Domain Controller? Which is also acting
> >>> like a DNS server.
> >>>
> >>> Best regards
> >>> Dead
|