Remote access and VPN

[Jack Spratt]

I run Server 2003. A couple of days ago I added "Remote Access / VPN Server"
through the "Manage Computer" window to the server so I can VPN in. Up to
that point my DNS was working fine and I could ping the server from a
workstation by the name. After the install not only can I not ping the server
by name but it has disappeared from the "Microsoft Windows Network" list in
Explore.

On the server I can ping itself by the name but on the network it can only
be accessed by entering the IP address (RDP).

I removed "Remote Access / VPN Server" and I remain with the same issue.
What have I done wrong? Where do I go to correct this change. It is very
important that I can access the server by name and not IP.

Thanks.
Jack

 

[Phillip Windell]

I run Server 2003. A couple of days ago I added "Remote Access / VPN
Server"
through the "Manage Computer" window to the server so I can VPN in. Up to
that point my DNS was working fine and I could ping the server from a
workstation by the name. After the install not only can I not ping the
server
by name but it has disappeared from the "Microsoft Windows Network" list
in
Explore.

On the server I can ping itself by the name but on the network it can only
be accessed by entering the IP address (RDP).

I removed "Remote Access / VPN Server" and I remain with the same issue.
What have I done wrong? Where do I go to correct this change. It is very
important that I can access the server by name and not IP.

Undo what you did.
Do not do this with a Domain Controller
Do not multi-home a Domain Controller,...RRAS/VPN constitutes
"multi-homing".
RRAS/VPN should run on a Member Server.

292822 - Name resolution and connectivity issues on a Routing and Remote
Access Server that also runs DNS or WINS
http://support.microsoft.com/kb/292822/en-us

272294 - Active Directory Communication Fails on Multihomed Domain
Controllers
http://support.microsoft.com/default.aspx?scid=kb;en-us;272294

191611 - Symptoms of Multihomed Browsers
http://support.microsoft.com/default.aspx?scid=kb;EN-US;191611


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[Jack Spratt]

Thanks. I'm going to work through this. Will reply afterwards.

 

[Jack Spratt]

Your first staement was to undo what I did, which I have attempted. The three
articles appear more to do with setting it up or correcting any glitches. Is
there a page where I can go through everything behind the scenes and reverse
the changes that were made because I have uninstalled the RRAS/VPN and the
problem still exists. Somethings were changed that were not reset on the
removal of RRAS/VPN.

Thanks.

 

[Jack Spratt]

I can ping the fully qualified name COMPUTERNAME.DOMAIN.LOCAL. Would like to
have it so I can just ping the computer name like I could prior to installing
the Remote Access / VPN Connection.

 

[Phillip Windell]

Your first staement was to undo what I did, which I have attempted. The
three
articles appear more to do with setting it up or correcting any glitches.

Yes the articles try to guide you to setting it up so it works in spike of
recommendations to not do it. A lot of people won't listen and will insist
on doing it anyway. But my intent is giving the links is to show the hassels
of trying to do it and to discourage doing it.

there a page where I can go through everything behind the scenes and
reverse
the changes that were made because I have uninstalled the RRAS/VPN and the
problem still exists. Somethings were changed that were not reset on the
removal of RRAS/VPN.

I'm not sure what would have happened that is still lingering, I can only
make guesses.

Perhaps the binding order is out of wack. The single main LAN Interface
must be first in the binding order.
Properties of Net'Places,..Advanced from top menu,...Advanced Settings from
drop down menu,...upper dialog box, use "side arrows" to adjust.

Then I would make sure in DNS (and WINS if you use it) that there are no
lingering records left over associated with the identity of that server via
the RRAS Interface that might cause there to be "confusion" while attempting
to resolve the machine's name.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[Jack Spratt]

Thanks. I tend to try to follow guidelines since doing workarounds don't
always work flawlessly. I wasn't aware this was one of the things I should
not do.

 

[Phillip Windell]

Did you check over any of those things I suggested at the bottom of the
post? Is it working correctly yet?

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[Jack Spratt]

The Binding was out of order so I moved it to the top. My records show
correctly, I believe, in the DNS.

I can't reboot the machine since I have a number of users RDPing into the
server I can't reboot, Is there a service I need to restart to implement the
Binding change? I'm still not able to ping the computer name from the desktop
and its not showing up in the "Network Neighborhood" from my desktop.

 

[Phillip Windell]

The Binding was out of order so I moved it to the top. My records show
correctly, I believe, in the DNS.

I can't reboot the machine since I have a number of users RDPing into the
server I can't reboot, Is there a service I need to restart to implement
the
Binding change? I'm still not able to ping the computer name from the
desktop
and its not showing up in the "Network Neighborhood" from my desktop.

Just wait till you have a chance to reboot it. You might want to just try
and right-click on the connection and choose "repair". It you have the
network icon down by the clock you can do it right there, but still wait
till the TS users are gone since even that may break their sessions. The
"repair" process actually does as much or maybe more than a reboot. Then
stop/start the DNS service, or just reboot. After all that it should
accomplish something.

Also keep in mind the Client you are trying to resolve "from" can also be an
issue because they will cache DNS queries for about,...what?,...30 minutes
or something like that? So rebooting or doing the network repair thing
isn't a bad thing to do with them either.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[Jack Spratt]

No go, I still can see the server computer name from the desktop.

Since I can ping the fully qualified name of the server from the desktop and
not the server computer name does this mean my issue is in the DNS?
("ServerName" vs. "ServerName.Domain.Local")

Thanks.

 

[Phillip Windell]

No go, I still can see the server computer name from the desktop.

Since I can ping the fully qualified name of the server from the desktop
and
not the server computer name does this mean my issue is in the DNS?
("ServerName" vs. "ServerName.Domain.Local")

That is completely backwards from what I thought you had. I thought the
machine name worked,..the FQDN did not.

I don't know what to tell. There are just too many variables for me to deal
with that. It could be anything from incorrect DNS Suffixes done statically
on the clients or pushed out with DHCP,..to,..Netbios over TCP/IP being
disabled,...to maybe some service not running that should be running. I
don't know.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

[Jack Spratt]

I learn as I go so it's time to learn a lot more. Thanks for your time on this.

 

[Jack Spratt]

Thanks Phillip I can now access the machine name. I originally could not ping
the machine name from my laptop but from other desktops the machine name is
completely available. A lot of stress is now gone and I won't be trying to
install Remote Access / VPN server on this machine.

Very much appreciate your help in regards to the Binding, I would not have
thought of that.

Jack

 

[Phillip Windell]

Very good!

Good luck with all those things, Sir!

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------