Re: Network settings conflict

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Liam (hoth_at_telus.net)
Date: 01/21/05


Date: Thu, 20 Jan 2005 22:41:50 -0800

Thanks again Super,

We are attempting to use the proprietary VPN software that comes with the
Symantec 360r gateway.
We have turned off ISA and are not using the VPN witihin SBS.
I can connect to the gateway with the error message "...192.168.10.0 is
conflicting with your network settings..."
all i do is hit OK and look at the Symantec log file and I can see that I
have a good connection BUT
I cannot see the domain.

Now....here is a twist:
If I look in Remote Routing and Access Under services it is disabled!
I try to start it and it wont start.
I googled a MS Knowledge base article that showed that veritas can disable
this.
We are using Veritas 9.1 for SBS 2003 so I thought it would be OK but
So I looked to see if the device that Veritas is using to back up to was
working...it is...WITH errors.
I tried to reinstall the drivers for HP DAT 40 x 6 and it made no difference
and RAS is still in the stopped position.
(I am at home now and cannot find the exact article)

So, enough information?
Thanks for all your help.

Liam

"SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
news:eTgU8b2$EHA.4072@TK2MSFTNGP10.phx.gbl...
> yes, the router will automatically add a route to the _network_, I see no
> problem with this information appearing in the router.
>
> the message "192.186.10.0 is conflicting with your network settings...see
> your administrator for help.", on what machine and after doing what did
this
> occur?
>
> I strongly advise not changing anything for a moment and giving us the
full
> output of 'ipconfig /all > C:\ipconfig.txt' from the server as it is
> currently configured. You are using a nonroutable private subnet, you're
not
> giving hackers anything by posting it here.
>
> "Liam" <hoth@telus.net> wrote in message
> news:%23CKmeV2$EHA.2192@TK2MSFTNGP14.phx.gbl...
> > Thanks for your input Super
> >
> > I used the .14 and .13 BUT in the routing table in the SGS 360R, there
ia
> > an
> > entry for 192.168.10.0
> >
> > No one in the office is taking responsibility for how this mysteriously
> > got
> > there. I figured that it was a self populating feild determined by some
> > rules.
> >
> > You know what I mean: "built by software engineers FOR software
> > engineers"!
> > lol
> >
> > Liam
> >
> > "SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
> > news:OwfEGD2$EHA.1300@TK2MSFTNGP14.phx.gbl...
> >> in an IP network there are two special addresses, the lowest address in
> > the
> >> subnet is the 'network' address, the highest address in the subnet is
the
> >> 'broadcast' address.
> >>
> >> It sounds like you are using a 24 bit mask, otherwise notated as
> >> 255.255.255.0
> >>
> >> In a /24 network .0 is the network address and .255 is the broadcast
> >> address. They are not usable addresses.
> >>
> >> Did you indeed use .13 and .14 or attempt to use .0? (for one or other
> >> device)
> >>
> >> "Hoth" <Hoth@discussions.microsoft.com> wrote in message
> >> news:6B712D4A-632C-4DBC-A6DD-756E2B4AD426@microsoft.com...
> >> > Thanks for your help Cris.
> >> >
> >> > I implemented the changes and had an unusual error.
> >> > No error code just this: "192.186.10.0 is conflicting with your
network
> >> > settings...see your administrator for help."
> >> >
> >> > I went into the symantec router and found the routing tables.
> >> > The first entry in the table is for 192.168.10.0 witht he metric 1!
> >> > So it is always going to be be attempted first.
> >> > I clicked OK on the error message box and the symantec client
log-file
> >> > said
> >> > connected.
> >> > I went to network neighbourhood and tried to connect to the domain to
> >> > no
> >> > avail.
> >> >
> >> > I did not do the original installation and I think their are some
> > serious
> >> > errors in this configuration.
> >> >
> >> > For instance the Routing and Remote Access, under Services and
> >> > Applications,
> >> > is always disabled??
> >> >
> >> > I am not sure how to proceed,
> >> >
> >> > Liam
> >> >
> >> > "Cris Hanna [SBS-MVP]" wrote:
> >> >
> >> >> Can we assume that you have one nic in the Server (which by the way
is
> >> >> not
> >> >> necessarily the recommended setup)
> >> >>
> >> >> IP 192.168.10.13
> >> >> SUB 255.255.255.0
> >> >> Gateway: Blank
> >> >> DNS/Wins 192.168.10.13
> >> >>
> >> >> Symantec
> >> >> LAN Port 192.168.10.14
> >> >> SUB 255.255.255.0
> >> >> Gateway 192.168.10.13
> >> >> WAN IP: 24.XXX.XXX.XXX
> >> >>
> >> >> Make those mods and see if things arent better
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Cris Hanna [SBS - MVP]
> >> >> ---------------------------------------
> >> >> Please reply only to the newsgroup and not to me directly so that
> >> >> everyone
> >> >> can benefit from the information
> >> >> "Hoth" <Hoth@discussions.microsoft.com> wrote in message
> >> >> news:AC223741-3352-408C-BB81-318880208926@microsoft.com...
> >> >> > Greetings,
> >> >> >
> >> >> > I am trying toVPN into my network.
> >> >> > Routing and Remote Access, under Services and Applications, will
not
> >> >> > start.
> >> >> > I do not know why?
> >> >> >
> >> >> > Here are my settings:
> >> >> >
> >> >> > IP: 192.168.10.13
> >> >> > Mask: 255.255.254.0
> >> >> > Default Gateway:192.168.10.15
> >> >> > DNS/WINS:192.168.10.13
> >> >> >
> >> >> > Symantec Gateway 360R
> >> >> > IP: 192.168.10.14
> >> >> > MAsk: 255.255.254.0
> >> >> > Gateway: 192.168.10.15
> >> >> > WAN IP: 24.xxx.xxx.xxx
> >> >> >
> >> >> > Connect from External Network
> >> >> > Linksys Router
> >> >> > WAN IP: 24.xxx.xxx.xxx
> >> >> > Lan IP: 192.168.10.15
> >> >> >
> >> >> > I use the Symantec VPN client software and tunnel through to the
SBS
> >> >> > LAN,
> >> >> > I receive this error message:
> >> >> > "network settings conflict with current network settings."
> >> >> >
> >> >> > Any ideas?
> >> >> >
> >> >> > Liam
> >> >>
> >> >>
> >> >>
> >>
> >>
> >
> >
>
>



Relevant Pages

  • Symantec spam filtering
    ... We currently use several products within the Symantec Enterprise Edition package. ... The DNS MX records send email to the gateway product, and then the gateway product relays ... the gateway product has blocked 1901 emails via the heuristics spam engine. ...
    (microsoft.public.exchange2000.admin)
  • Re: Firewall noch sicher?
    ... Wir habe hier noch eine Symantec Gateway Security 320 Appliance die ... In der Regel kann man, Rechner sauber konfiguriert, Firewalls aller Art ... Andreas (PGP Key available on public key servers) ...
    (de.comp.security.firewall)
  • Re: Sybari or Trendmicro?
    ... I don't know about Symantec Mail Security for Exchange. ... Symantec AV for SMTP ... gateway is a decent product, ... already using Symantec AV product to protect our Exchange server, ...
    (microsoft.public.exchange.admin)
  • Re: email not coming in from specific domain
    ... I had that particular domain whitelisted in both the Symantec Mail Securty for MS Exchange and the ... SMTP for Gateways. ... for sure how many emails they have attempted to send. ... ran some SMTP commands against the Gateway machine, ...
    (microsoft.public.exchange2000.admin)
  • Re: Firewall noch sicher?
    ... Wir habe hier noch eine Symantec Gateway Security 320 Appliance die ... Gateway oder ist es ein interner Angreifer? ... Also leb einfach damit, dass die Kiste evtl. ... der dazu verwendbaren Werkzeuge verknackt wird. ...
    (de.comp.security.firewall)