General discussion

Locked

Dialup to NT 4 problems

By gcwoods ·
NT 4.5SBS server, with Win9x Worstations. Exchange 5.5
I have a Laptop, which is used in the office and now is required for dial in use from home. I have read many of the suggestions here but no luck. Tried profiles without PCMCIA Netcard, TCP/IP only, and then I cannot even see local pc on network, but can dial in and ping server, email to exchange 5.5 works but no network drives avail.
I have successfully configured a PC not previously set up to connect to the server, and can map drives etc, everything fine on that one.
I must maintain the laptop for connecting using netcard when back in the office.
Re-enabling the PCMCIA Netcard - Can still dial in, lets me see the local \\pc but not the \\server (when browsing / & at DOS prompt, can ping server, email, but no mapping drives etc.
Help please

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Dialup to NT 4 problems

by Brian Lusk In reply to Dialup to NT 4 problems

It sounds like your browse listing is the problem. However, before I can be sure, I need to know more information.

1. Can you manually map a drive using the "NET USE" command from the command prompt? (i.e. net use u: \\server\user)
2. If you can't use the name, can you use the IP address? (i.e. net use u: \\10.10.10.1\user)

Odds are, if you can map manually, the problem is the default protocol being used. You will want to have two different profiles, all right, but the difference will need to be this:

Go into Network Properties
In there, you should see a listing like this:
Client for Microsoft Networks
PCMCIA Network Card
Dial-up Adapter
TCP/IP -> PCMCIA Network Card
TCP/IP -> Dial-up Adapter

Bring up the properties for TCP/IP -> Dial-up Adapter. Under the Advanced tab, you should have an option for "Make this the default protocol"

Your other profile will need to have the PCMCIA adapter as the default.

Hope this helps!
Brian Lusk
brianlusk@netzero.net (email if you

Collapse -

Dialup to NT 4 problems

by gcwoods In reply to Dialup to NT 4 problems

Thanks for your reply, I managed to get the laptop to log in and receive all the normal priviledges, but to do it I had to force the DUN TCP/IP settings to a fixed IP address, while this works now, if another line is required a second IP address will be required and this will change things again no doubt..!
With this config, I'm not even using two seperate Hardware profiles..!

Collapse -

Dialup to NT 4 problems

by vijaychandran In reply to Dialup to NT 4 problems

check with your network / RAS-server administrator that he has enabled browsing to other PCs on the network. there is an option in the RAS server properties for "access to this PC only " for dial-up clients. this option will prevent you from seeing other PCs on the network except the server. and for the server he has to give you shares to be seen over the dial_up connection.

Secondly the IP address assigned for the dial_up clients has to be in the same as of the internal LAN to see other PCs.

Collapse -

Dialup to NT 4 problems

by gcwoods In reply to Dialup to NT 4 problems

Thanks for the reply, but I was able to dial in to the server from other desktops OK, just the laptop config was bugging me....!

Collapse -

Dialup to NT 4 problems

by gcwoods In reply to Dialup to NT 4 problems

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums