Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 240
  • Last Modified:

win2k server DUN + static routes

I have

win2k server

1 gateway ip that is assigned to the DUN ISDN ppp link

8 ips (subnet mask 255.255.255.248) these are all routed from my isp through my gateway

motorola bitsurfer pro ISDN modem

4 computers total (all with static ip's)



I have a small home computer network.  The problem is that the first time I dial up after rebooting my win2k server, it ALWAYS connects, but doesn't route correctly.  The first time I connect to my isp after a reboot, it seems (by watching the network lights) like it is trying to route through my LAN instead of the DUN like it is supposed to.  If I disconnect and dial back again, then everything works perfectly!  Then any subsequent dials again without rebooting also work perfectly.

what the heck is going on here?  what would cause this to happen and how can I go about fixing it?

0
SD_Adept
Asked:
SD_Adept
  • 2
1 Solution
 
pabgilanCommented:
I am not an expert ath this themes, but I have a DUN connection with my ISP and an Ethernet LAN and I am not having this problem.

There are several IP ranges reserved to use in LANs to avoid routing problems; IP numbers within these ranges are not used in Internet, only for LANs not directly accesible from Internet.

Example:

My machines are using 172.16.1.1, 172.16.1.2 and so on as their IP addresses of their Ethernet cards.

My netmask is 255.255.0.0 (class B subnet, I think)

This is one of these kind of "international reserved LAN IP ranges" I am saying

I hope this helps
0
 
SD_AdeptAuthor Commented:
no.  The IP's I have are entirely valid.  I'm not using proxies or port tricks, this is real routing.  Like my original comment said, my isp knows to route these ip's through my DUN.  The problem is that after the first time dialup, it always tries to route through my network instead of the internet.  :/
0
 
epaulCommented:
"Default Gateway" entry from internal adapter's IP-seting must be empty. Check it.
0
 
SD_AdeptAuthor Commented:
you win the prize.  :-)  I had the default gateway set to the dialup adapters's IP.  Removing that fixed the problems.

thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now