General discussion

Locked

Ping fails via RAS but works via LAN

By wml ·
Problem is with dialling in (connecting through NT4 Server) to connect to our Terminal Server box so users can run a session using the new accounts software: it worked initially, but subsequently failed to find the Terminal Server machine or find the host name. So I tried ping which leads me to think its a network problem not a Citrix/Terminal Server one.

When I establish a dial-up connection to the NT4 server and then ping this server with its ip address, it times out; pinging any server byname comes back with host unknown.
The fact that everything works across the LAN suggests its a RAS -related issue.
Any ideas gratefully accepted!

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Ping fails via RAS but works via LAN

by Craig IT Mangaer In reply to Ping fails via RAS but wo ...

I have had problems with NT's RAS and TCP/IP as in it doesn't seem to work all the time. You could do a couple of things to test the problem Try adding NetBeui as a protocol or use a external modem pool (the method I am using). The external modem pool seems to help in the request of IP addressing for dialup networking as well as establish it as a working protocol more often. And of course it adds a nice extra security layer. Intel has a LAN Rover product that works fairly nice and has several nice options that go with it for a reasonable price.

Collapse -

Ping fails via RAS but works via LAN

by wml In reply to Ping fails via RAS but wo ...

Poster rated this answer

Collapse -

Ping fails via RAS but works via LAN

by jsewell In reply to Ping fails via RAS but wo ...

1. Make sure you have the ip of the TServer in your hosts file.
2. run ipconfig /release.
3. dial -in
4. do a route print and make sure the default gateway to you domains subnet is the dnis's assigned by thr ras server. if not, manually add theroute.....If you need a more detailed break-down or this doesn't work, let me know.....

Collapse -

Ping fails via RAS but works via LAN

by wml In reply to Ping fails via RAS but wo ...

Not clear on this - dialling in from a Win98 pc. DNS not used on the server. Problem is I can't even ping the NT server that I dial in to over RAS, let alone the Terminal server. Can a Win98 client use an equivalent to lmhost file?
Or could I set up a fixed ip address for the client dial-up adapter and map a route on NT server to this address?

Collapse -

Ping fails via RAS but works via LAN

by jluna In reply to Ping fails via RAS but wo ...

Sounds to me like a DNS issue, you may want to check your DNS setting.

Or you could also specify a static mapping in your WINS server for the Terminal server.

Hope this helps.

Collapse -

Ping fails via RAS but works via LAN

by wml In reply to Ping fails via RAS but wo ...

Poster rated this answer

Collapse -

Ping fails via RAS but works via LAN

by freddie_t_wong In reply to Ping fails via RAS but wo ...

Create a LMHOST file on your client computer connecting through RAS.

LMHOST should contain the IP and server names.

Collapse -

Ping fails via RAS but works via LAN

by wml In reply to Ping fails via RAS but wo ...

Poster rated this answer

Collapse -

Ping fails via RAS but works via LAN

by tchantre In reply to Ping fails via RAS but wo ...

I also have had a similar problem where when there is a modem and an ethernet (lan) card installed on the win 98 client they can connect to our mailserver, but not with a dial up connection. when we remove the ethernet card the dial up session to retrive mail works fine. also when both cards are present you can't ping the mail server but yet you can surf the net during a dialup.

Collapse -

Ping fails via RAS but works via LAN

by wml In reply to Ping fails via RAS but wo ...

What I eventaully found was that the ip address of the nic on the RAS client dialling in inteferes with the connection:
When Windows 98 dials into the RAS server and requests a specific IP
address the RAS server may deny the request (for whateverreason) and in
that case the client gets allocated an IP address from the DHCP pool.
If a client dials in using RAS but tries to access an IP address on the same subnet as it's network card (even though it is not connected to the network) the PC will try to connect via the network card and not the dial-up adapter so it won't get anywhere.
Disabling the nic on RAS client (using profiles) works.

Back to Windows Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums