8 replies
by lylea42
by rodger
by curlergirl
by rodger
by mckaytech
The NIC going to your DSL router will need to be set with one of the IP addresses leased from your ISP - theoretically, you could actually bind more than one to that NIC if you wanted but these must be real IP addresses.
The other NIC could be any addresses you wanted but in the interests of protecting the Internet against configuration errors, you should choose addresses in one of the private IP address ranges.
I don't have enough experience with the Cisco 675 to speak with authority, but it seems to me it should not be in bridging mode.
paul
by rodger
by stemarie
The NIC connected on the Router side needs a public IP (one of the 5), the other needs a private ip (one of the 10.0.0.0).
The Router does NOT need tampering with, if it works now, then it will continue to work.
The router should not operate in bridging mode since this re-transmits broadcasts, you don't want this unless you have another subnet on the other side that needs to be aware of broadcasts. (Like an NT domain controler)
My advice: Don't touch the router and get a big book on microsoft proxy, especially if you plan to use the IIS service in-house for intranet publishing. If you don't get proper documentation, you're gonna cry, I guaranty it.
Why ?
Well Microsoft proxy installs a new winsock.dll on all client machines,they make a DCOM call on the proxy machine which then decides were the network call goes.
The proxy has to know what's inside and what's not, and you can't (unless you jump through flamming hoops backwards, blindfolded) host virtual websites on the private side on th
by rodger
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending