RE: Sudden connection problems on MS Windows Server 2003 SP1

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

Okay. Your VPN clients are getting the wrong gateway. It is the only thing
that I can think of. Have you checked the "Use Default Gateway" Box when
setting up the VPN?

I have a Server2K3 machine behind a router that has 2 NIC cards and the same
thing was happening to my hosts on the internal network (not connected to the
server, but receiving DHCP from it). They would sometimes (usually after a
day or two) lose connectivity to the internet. Restarting the server would
correct the problem. I found the problem to be that the server's DHCP was
giving the wrong gateway.

I think you have a gateway problem here with your VPN connection.

"Oskar" wrote:

> But in that case would they be able to connect to the server at all, not
> talking about working on it for a couple of days. The clients don't resolve
> the server name in DNS instead they use an ODBC server definition (a
> configuration file on the client) to get the IP address of the server. You're
> right though - our public DNS server doesn't have records for the internal
> hosts.
>
> "Eric the IT Idiot" wrote:
>
> > I think that you should only be specifying the IP address of your internal
> > DNS server.
> >
> > Your VPN clients are being sent out to the other DNS server to try to
> > resolve the your internal network.
> >
> > If forwarding is set up on your internal DNS server to your ISP DNS servers
> > then everything should work okay.
> >
> > Get rid of the External DNS server's IP address on your TCP/IP properties.
> >
> > "Oskar" wrote:
> >
> > > The IP config looks like this:
> > >
> > > Windows IP Configuration
> > >
> > > Host Name . . . . . . . . . . . . : w2k3srv
> > > Primary Dns Suffix . . . . . . . :
> > > Node Type . . . . . . . . . . . . : Unknown
> > > IP Routing Enabled. . . . . . . . : No
> > > WINS Proxy Enabled. . . . . . . . : No
> > >
> > > Ethernet adapter Local Area Connection:
> > >
> > > Connection-specific DNS Suffix . :
> > > Description . . . . . . . . . . . : HP NC7782 Gigabit Server Adapter
> > > Physical Address. . . . . . . . . : 00-13-21-10-A8-1E
> > > DHCP Enabled. . . . . . . . . . . : No
> > > IP Address. . . . . . . . . . . . : 192.168.5.22
> > > Subnet Mask . . . . . . . . . . . : 255.255.248.0
> > > Default Gateway . . . . . . . . . : 192.168.5.254
> > > DNS Servers . . . . . . . . . . . : 192.168.5.39
> > > 203.128.145.191
> > >
> > > "Eric the IT Idiot" wrote:
> > >
> > > > Please give an ipconfig /all so that we can further diagnose the problem.
> > > >
> > > > "Oskar" wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > I have the following setup: MS Windows Server 2003 SP1 machine with MS SQL
> > > > > Server SP3 on it. Clients are using an application, which is using ODBC
> > > > > drivers to connect to the database server. Some of them are connected to a
> > > > > LAN, others connect trough a VPN from branch office computers, which are
> > > > > behind the firewall and some routers.
> > > > >
> > > > > The problem is that everything was working fine for a day and a half until
> > > > > suddenly the branch office users started complaining about the application
> > > > > hanging after the logon process. I saw no error messages on the DB server
> > > > > machine, neither in the System or Application logs. I checked for errors on
> > > > > the NIC but I didn't find any. I checked the SQL Server error log and found
> > > > > nothing wrong. No hardware errors as well. The "network guys" didn't see
> > > > > anything suspicious in their firewall logs or in the network sniffer trace,
> > > > > they said everything looks fine. At the same time users whose computers were
> > > > > connected to the LAN could connect to and work on the database server without
> > > > > any problems.
> > > > >
> > > > > We restarted the Windows Server 2003 SP1 machine and users from branch
> > > > > offices regained their ability to use the application to connect to the
> > > > > database server.
> > > > >
> > > > > Do you know why is this happening?
> > > > >
> > > > > --
> > > > > Many thanks,
> > > > > Oskar
> > > > >
.

Quantcast