Re: Windows Server 2003 R2 x64 RRAS seems to be limiting connectio

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Also, you have disabled DHCP server on the AP (if it does it) and done an "ipconfig /all" to verify that the correct default gateway is being assigned to wireless clients?

Kurt

Mark Wilson wrote:
Thanks for getting back to me on this Addy.

Just to clarify, the 192.168.17.0 network (LAN1) is a mixture of wired (100Mbps) and wireless (54Mbps) - the access point (192.168.17.254) is a separate device to the ADSL router (192.168.17.1) and clients on that network can use wired or wireless connections to contact the DHCP server and get a 192.168.17.x address.

The route on the ADSL modem (router) is to ensure that the default gateway knows where to send packets for LAN2 (it's the way that I was advised to set this up when I had ISA between the two networks, instead of RRAS)

There is no WiFi on LAN2 but wired connections on the 192.168.11.0 subnet work with no issue. It's only when I'm connected to the 192.168.17.0 subnet that I have a problem (wired or wireless); hence the reason I suspect my RRAS config.

Finally, I'm not getting any sensible error messages (hence my frustration!), just lots of timeouts, files that never open etc. I had wondered if this was a firewall issue but I can browse to the shares OK...

Very odd!

Mark

"addy" wrote:

Hi Mark

I couldn't quite catch the WiFi Bit. What is the range of IP addresses
assgned to the WiFi Clients? What's with the route on the ADSL modem
is that your AP(Access point) ? if yes the it would mean the clients
on WiFi would be in 192.168.17.0/24 subnet. You have a gateway at
192.168.17.2 set to your DSL router. You can access shares when you
are on WiFi in the 192.168.12.0/24 subnet the how could this be RRAS
issue. The file access is over SMB, IP cannot differentiate between
access to a file or browsing the share. Unless your NAS somehow
detects you don't have permissions on this particular share and throws
an access denied. Which leads me to another question what is the error
message which pops up when you access the files.


Could you clarify a bit more on this one.

Thanks
Aditya

.

Relevant Pages

  • Multihomed Win2k Server Routing Issue
    ... Multihomed Win2k Server, 2 NICs. ... of 192.168.1.xx clients connected. ... These clients have default gateway ... any machine in the 192.168.1.xx subnet no problem... ...
    (microsoft.public.win2000.ras_routing)
  • Re: DHCP clients; where does the preffered routes come from?
    ... "My question than is it looks like my DHCP clients are picking up a ... gateway of 192.168.2.5 where is this value coming from, if my DHCP ... gateway for clients on the 192.168.1.x subnet. ...
    (microsoft.public.windows.server.networking)
  • Re: Windows Server 2003 R2 x64 RRAS seems to be limiting connectio
    ... the 192.168.17.0 network is a mixture of wired ... The route on the ADSL modem is to ensure that the default gateway knows where to send packets for LAN2 ... There is no WiFi on LAN2 but wired connections on the 192.168.11.0 subnet work with no issue. ... It's only when I'm connected to the 192.168.17.0 subnet that I have a problem; hence the reason I suspect my RRAS config. ...
    (microsoft.public.win2000.ras_routing)
  • Re: Creating a Gateway
    ... configuration file for the gateway. ... The clients on each subnet having gateway addresses like my ... First tests would be clients pinging their gateway, ...
    (Fedora)
  • Re: How to configure Linux as a router
    ... For the clients on the 10.0.1.x subnet, you need to either set their ... default gateway to 10.0.1.93, or enter a route for the other subnet ... Here is a routing table on ...
    (comp.os.linux)