Re: Win2k Ras/VPN and a SCO Unix Machine and some difficulty getting to the SCO Machine [LONG]



Bill Vermillion wrote:
All of my comments will be SWAGs as it's sort of hard to envision
everything. I'm a hands on type person :-)

I understand completely - SWAG's are perfectly acceptable and it is hard to
picture - I've seen it several times and still had to get them to confirm a
couple things for me even though I had it diagramed notes. And its real hard
to explain visually.

The first suggestion I'll make is to forget DHCP and go with static
addresses. Or set your DHCP up to always give the servers the same
IP addresses and the same for the routers.

I'll go ahhead and answer one question here - yes all the servers have fixed IP
addresses, some/all of the workstations that connect via Ethernet also now have
fixed IP, same with the Linksys devices as well. Only thing that currently use
DHCP would be some workstation via ethernet or a wireless connection and then
the VPN connections using the VPN server and its IP range.

I've seen more than one environment when DHCP was setup because it
was 'easy' [a loose translation for "I don't know what the hell I'm
doing so I'll let the SW do it all for me"]

ditto

Both NICs on the Windows 2k machine connected to hub:
192.168.1.252 LAN Uses a gateway of .254 but set to use itself
for DNS. 192.168.1.253 WAN Uses .254 for the Gateway and for
DNS 192.168.1.192 is the target IP for the VPN with a mask
of 255.255.255.224 and the range of VPN IP addresses is from
192.168.1.200 to 192.168.1.219 with the 200 being reserved for
the VPN Server IP.

Why is the W2K machine using itself for DNS and not the .254
address as all other machines are. Could the DNS in the machines
not be consitant. That could cause problems.

That was one of my concerns as well and with the way they are cabled and to be
on the same subnet and then one is supposed to be a WAN and one a LAN
connection they really blow my mind.

It reminds me of a quote I read to today when Pauline Kiel [film
critic at the NYT at one time] was lecturing to a class at
a well known southern university. "It's true that probably
90 percent of the people in every profession are incompetent"
From what I've seen at times, I could almost think that number was
conservative.

ditto

I also imagine the LAN NIC set to use itself for DNS is probably
also a problem and the VPN on the same subnet could also be
confusing.

I'd personally go for ONE DNS - so you can always check it's
integrity.

I can do that - I thought about doing it last time I was looking at it but got
cold feet. Their network does work although not as well as it should

To reiterate - my first thought is to get only one DNS running if
at all possible.

I can do that.

Sorry for rambling on - but as others know - that's my style :-)

I am grateful for the input - your not rambling to me.

.



Relevant Pages

  • Re: DNS DHCP Domain
    ... site 2 firewall allow access from that address space? ... My Vpn is on teh same subnet as site 1 but with a 50 ip reservation. ... So that should not be the problem, look if your VPN server allows ... So the linux box cannot update it's DNS entries from the master DNS ...
    (comp.os.linux.networking)
  • Odd VPN name resolution problem. Please...
    ... There are lots of posts about VPN name resolution problems. ... The machines are running either Win2k ... pro or XP pro. ... The VPN server machine name *doesn't always* appear in "My Network ...
    (microsoft.public.win2000.networking)
  • Re: VPN and DNS issues
    ... you should have your internal DNS in the VPN server and the VPN server assign the DNS to the client. ...
    (microsoft.public.windows.server.networking)
  • Re: VPN server (hardware) and VPN client (Software) - both with changing IP. Can it be?
    ... How many clients will be using the VPN functionality simultanesously? ... >to have VPN server as a hardware box and client could be software. ... >For server we have registered with dyndns.org, so we have constant dns name ... what VPN server box would you recommend to buy? ...
    (comp.security.firewalls)
  • Re: VPN users cannot see domain shares
    ... > I have a a windows xp machine that succesfully connects to a windows ... > 2003 domain via VPN. ... Register all machines as WINS clients on their NIC-IP ... properties and make sure the VPN server also assigns ...
    (microsoft.public.win2000.networking)