It's all about routing...
How about a hardware solution...Use 2 - Netgear FVS318 routers...and create a hardware vpn tunnel...between the 2 networks..This can be always on..or limited to certain times...
Your 2 networks must be be privately addressed on different subnets but the FVS318...
Okay I need a sample...Followed some instructios on web but think maybe they were wrong...DNS server on W2k
Address 192.168.1.10
Server fs1.mydomain.com
To create reverse lookup zone in dns...do I enter the numbers 192.168.1-inaddr-arp
or 10.1.168-inaddr-arp
I'm obviously confused...
Any...
Okay..similar situation...New Exchange Server...Several old users..(which I think were not necessarily real people) were set up on old server..Not set up on new...All they get is spam...Lots of NDRS..
Don't want to add user...and have to clean out..all the time..Like blackhole idea but need...
Yes..to is the isp dns causing the problem..You must list the server as the primary dns under tcp/ip on your domain workstations...The isp's dns does not know anything about your internal network...
I'm assuming that you have setup a dns server...and that you have appropriately configured its...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.