Re: WOW - Changing Network Subnet on SBS2003 Got me crazy

From: Peter (Peter_at_discussions.microsoft.com)
Date: 03/01/05 

Date: Tue, 1 Mar 2005 12:29:07 -0800

OK-

That solved my immediate problem now I am left with another which was just
created and I had had previously in the past and don't know how I fixed it.

Problem: VPN and not able to access network shares

I have been through every help site available and cannot find a fix.
I have tried multiple scenarios to no avail.
I have tried the reg fixes along with dns pointer records along with
enabling and disabling netbios over tcpip per different microsoft tech reports
I have tried a local Lmhosts file per a subscriber's earlier explanation
I have tried setting a separate different static address pool in Remote
Access for Remote clients
I have tried all this, restarted/started dns & netlogon, cleared server Wins
cache, clear nbtstat cache, cleared dns cache all along the way...
I have tried more also

What I can do:

pickup exchange e-mail from the SBS 2003 server, which is also the Remote
access server
view files on the SBS server via \\SBSserver\ from folder address line
ping all office machines by name from vpn client
open files on remote machines by ip address: such as typing "
192.168.78.2/software" from a folder address line

What I cannot do:

Resolve host names from a client machine to access files and map drives

What I need to do:

I need the consistent ability for drive mappings to other office computers
to be accessed from vpn clients while on the road to update rental software,
etc.

Also, one client cannot even connect via VPN now.. it says "unable to
establish vpn connection."

I apologize for dumping all this - should I open a new thread? I am having
no breaks with this RAS now.

Sincerely,

Peter

"SuperGumby [SBS MVP]" wrote:

> if you had previously done some of the steps it would explain your current
> predicament.
>
> "Peter" <Peter@discussions.microsoft.com> wrote in message
> news:2ECF7A4E-0810-4A08-845B-73752C37867E@microsoft.com...
> > Very interesting. I had used some of those workarounds in the past. Is
> > it
> > possible those very workarounds are overriding my servers host record in
> > DNS?
> >
> > I cannot access this server right now ... as remote access is currently
> > offline and the office is closed... I will be there early in the morning.
> > Maybe I should remove those changes that are described in the article as
> > they
> > may be affecting my ability to set the server's host record in DNS?
> >
> > Peter
> >
> > "SuperGumby [SBS MVP]" wrote:
> >
> >> can you do me a favour and just check your system against
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;292822 please.
> >>
> >> "Peter" <Peter@discussions.microsoft.com> wrote in message
> >> news:7BA25620-04E8-4B30-B2A6-05EEACAA13C5@microsoft.com...
> >> > Ok - I did not run "Change Server IP Address" Wizard to start - I did
> >> > it
> >> > manually. After doing so ... I changed WINS, DNS, the DHCP scope
> >> > ..etc...
> >> > no go.. SO I ran the "Change IP Address Wizard" and back again.. and
> >> > again..
> >> > then I ran CECIW afterwards as everyone says to do... I repeated this
> >> > process several times... I could get EVERYTHING just the way I want
> >> > EXCEPT:
> >> >
> >> > The DNS Host "A" Record for the Server. This record continually
> >> > changes
> >> > back to the original address that was set up on the server. I have
> >> > spent
> >> > hours trying different subnets .. . but like clockwork.. either 15
> >> > minutes
> >> > later or when I "reload" the DNS Forward Lookup it goes right back to
> >> > the
> >> > 192.168.1.1 address that was the original address.
> >> >
> >> > I need to change the address scope so that laptops can access the VPN
> >> > from
> >> > home linksys routers, hotels, etc... where the 192.168.1.0 network
> >> > exists
> >> > everywhere. I want to take the SBS network to an "unpopular" private
> >> > network
> >> > like... 192.168.78.0..
> >> >
> >> > but everytime I do it.. the server host record in DNS changes back to
> >> > 192.168.1.1 ... I have deleted this record and recreated it, changed
> >> > it,
> >> > deleted the reverse lookup also, and changed.. but SOMETHING keeps
> >> > changing
> >> > it back.
> >> >
> >> > Without the server resolving to the proper IP.. no exchange e-mail,
> >> > login
> >> > issues, no companyweb.... etc. SO.... if anybody knows what is
> >> > overriding
> >> > this host record setting like clockwork... I would be GREATLY
> >> > appreciative...
> >> >
> >> > Thank you in advance for reading through my issue.
> >> >
> >> >
> >>
> >>
> >>
>
>
>

Relevant Pages

  • Re: feeling dizzy about setting up a small remote office.
    ... | dcpromo a new server ... | - installed dns, killed the dns wizard ... | the remote end of the vpn tunnel. ... |> of the VPN router to its public IP address, ...
    (microsoft.public.windows.server.active_directory)
  • Re: VPN clients unable to connect to other resources.
    ... gateway matches the IP of the remote client, and DNS and WINS point to the ... remote (although it takes close to a minute to connect, ... This is just regular Windows VPN, ... VPN server, remote routing and access running on the SBS 2003 server ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with connectcomputer and active directory
    ... I understand that you would like to join a remote client to the domain. ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ... Create a VPN connection to ISA/RRAS on the Internet ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Server Access Issues
    ... I am using the SBS box as the VPN server and the WinXP clients are setting up ... generic VPN client as a few of the client machines with be MAC's. ... > You may want to ensure your VPN server is looking at the right DNS. ...
    (microsoft.public.windows.server.sbs)
Loading